neo

• fa v6 is no longer in beta, so neo switched to using the new version.
• workaround for a new bug in the disease API, returning undefined for certain dates

You can find all the details here: https://github.com/neomjs/neo/issues/2864

related to the globalThis changes

this version should make it possible to run the neo core inside a nodejs based env.

The package.json now contains "type": "module", which enforces all build scripts to be real modules. This ensures that future dependency updates won't break once they drop their support for commonJS.

After quite a bit of testing I assume that all programs work like before the refactoring. In case I missed something, please open a ticket.

I will work on the npx neo-app repo next, adding "type": "module" there as well. Once done, new workspaces will also contain the "type": "module" flag inside their package.json files.

Since the project contains .mjs inside its name, it felt good to finally get rid of the last commonJS based files, even when they were only inside the build scripts. The files use the .mjs extension.

https://www.youtube.com/watch?v=mr87o5kD_0k

https://youtu.be/li2VZ_VNqGM

1. getDomRect() shortcut for Neo.main.DomAccess.getBoundingClientRect()
2. dependencies update
3. added the last blog post to the website app
4. cleanup

https://github.com/neomjs/neo/blob/dev/test/siesta/tests/ClassConfigsAndFields.mjs

Blog post should get published tomorrow, stay tuned.

the work will happen inside a separate branch, since we need to replace all constructor methods with a custom construct method.

and a bit of house keeping: https://github.com/neomjs/neo/issues/2759

For the webpack related issue, take a look at: https://github.com/neomjs/neo/issues/2753

• dependencies update
• house keeping

• Website app: Added Safari to the non shared workers based dev mode examples
• Dependencies update