Update to Typescript 5.3.3 and associated updates

[vincentmarchetti]

I have forked the manifesto repository to support development of the API in handling 3D content. This development is being carried out by the IIIF 3D Technical Study Group. On cloning the IIIF-Commons/manifesto, and checking out the master branch, I found that on a fresh installation (fresh Node.js; fresh run of npm install ) there were several invalid or deprecated modules, and modules identified as vulnerable.

I created a branch "kshell-update-original-manifesto" in my repository https://github.com/vincentmarchetti/manifesto and updated the dependencies and configuration files, re-enabled the tests, and made a minor changes in one Typescript source code file, all described below and in the commit history. The result, at commit 9f709b0, Feb 10, is a package that builds without errors and runs the original suite of 200 tests with just one failed test. It's a significant change is some module versions, but if acceptable this can be submitted as a pull-request.

A summary of changes:

1. Updated the dependency on Typescript from 3.6.3 to 5.3.3

2. Replaced awesome-typescript-loader with ts-loader

3. update mocha (testing) from 2.2.4 to 10.2.0

4. updated typedoc (document generation) from 0.15 to 0.25.8

5. Restricted install dependency on module node-fetch to v2; the current v3 is incompatible with the manifesto typescript code

6. Several other module dependencies were updated as well.

7. Changed typescript source in in src/PropertyValue.ts. The javascript spread operator was throwing type errors. The spread operator was replaced by explicit iteration over lists.

8. All test cases were enabled. 203 passed, 1 failed, a method Sequence.getThumbs which is already marked in source as to-be deprecated.

[stephenwf]

Had a look at the changes:
IIIF-Commons/manifesto@master...vincentmarchetti:manifesto:3dtsg-dev

I think it all looks fine 👍 can remove that thumbs test. I think you're right - probably a major version with all the dependency changes, specifically Typescript. (cc @edsilv)

Is the 3D/scene work ready for experimenting now? I could have a look at adding a branch to https://github.com/iiif-commons/parser for basic support

[vincentmarchetti]

The work on 3D/scene is going on in three related projects
Editors have prepared a very initial draft of 3D extensions to the Presentation API https://github.com/IIIF/3d/blob/eds/temp-draft-4.md
There are a set of example manifests for 3D content at https://github.com/IIIF/3d/tree/eds/manifests
There is a plan for demo viewers that would display those manifests, the plan is at https://github.com/IIIF/3d/blob/main/demo/EXPERIMENTS.md . I am working on a demo viewer based on X3D and the X3DOM library, other demos are in development such as at https://codesandbox.io/p/sandbox/threejs-model-origin-lcwnlk

The 3D specs very much preliminary, but I think the basic properties of a Scene typ are stable. As well, the draft makes important use of the SpecificResource type from the Web Annotation model, and I don't think that is implemented in the manifesto class tree yet.