Deprecating some of the JS builds in the development CI

[lpugin]

Currently, the development CI workflow builds four versions of the JS toolkit. Several of them are not really necessary and this will change with the next release. The development phase of Verovio 3.11 will be the latest to include the following JS builds of the toolkit in the CI:

• verovio-toolkit.js
• verovio-toolkit-light.js
• verovio-toolkit-hum.js

After the release of 3.11, these will only be included in the releases but not in the development CI anymore. The CI will only include verovio-toolkit-wasm.js. This means that if you want to use the develop version after that you should use the verovio-toolkit-wasm.js build. This is the recommended version anyway because it is significantly faster.

In practice, it means that https://www.verovio.org/javascript/develop/verovio-toolkit.js will no longer exist. If you still want to use it, or one of the above versions, you will only be able to use the latest release, or a specific version. For example, https://www.verovio.org/javascript/latest/verovio-toolkit.js or https://www.verovio.org/javascript/3.10.0/verovio-toolkit.js. If you want to use the develop version, you should point https://www.verovio.org/javascript/develop/verovio-toolkit-wasm.js and adjust the way it is used.

Using the WASM build

The main difference when using the wasm build is that the toolkit loads asynchronously. It means that you need to wait for this to happen before using it. See the Getting started section for the reference book on how to use it.

Also note that the Module.onRuntimeInitialized might change to verovio.module.onRuntimeInitialized in the next release because of some refactoring for improving the NPM packages. See this discussion for more information about it.