os-js / osjs-dev-meta Goto Github PK

Testing suite belongs in this repo so that it can be locked globally instead of in the CI stages.

Makes it a heck of a lot easier to run tests locally as well, and out of the box.

Probably best to start with @^26 as it is today to ensure all tests run fine. Then upgrade to latest. This way packages with failing tests can just stage their update of this meta library.

Split out from os-js/osjs-client#185 (comment)

It's version locked in the CI because latest Jest seems to trigger some kind of edge case that leaves certain tests hanging. Haven't had time to look into it. Might actually just be a thing in the server codebase come to think of it.

Ideally it should be updated, and then be put into https://github.com/os-js/osjs-dev-meta instead of being in the CI stages.

Tasks

Stage 1

1. Include Jest 26 as a dependency (make sure it's installed with node 16 or below!)
   1. Update README
2. Upgrade dev-meta dependency on every package with tests, verify tests
   1. Remove the npm install -g jest from CI if verified

Stage 2

1. Upgrade to latest Jest
2. Upgrade dev-meta dependency on every package with tests, verify tests again and fix any errors

Related packages

• https://github.com/os-js/osjs-server
• https://github.com/os-js/osjs-client
• https://github.com/os-js/osjs-cli

Webpack 4 doesn't run on Node 17, which is a problem because this is the next LTS and some users run this as their main environment.

Also, Webpack 4 has a lot of dependencies that's not really required because the Node version requirement of OS.js is 12, which could be bumped to 14 without any impact.

So this will fix any issues related to webpack 4 and bring on some nice speed improvements both in build times and dependency installation.

Split out from:

• os-js/OS.js#785

Related:

• #26
• https://github.com/os-js/osjs-client/tree/feat/webpack-5

Tasks

Stage 1

Steps should probably be done with Node 16 or earlier.

Pretty much the same procedure as done in #24

• Upgrade Webpack
• Upgrade loaders and extensions (and replace any defunct stuff)
• Make this work on the client repo (osjs-client)
• Then ensure this works on the base repo (OS.js)
• Release as major version bump

Stage 2

This stage could probably be automated since anything in stage 1 will apply project-wide.

• Go through all packages using dev-meta, upgrade, test, release.

Would be nice to have a way to scan the webpack bundling results and place the source files (mainly .js and .css) into the metadata.json file automatically.

This needs a separate repo, and then be added to this meta package.