You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Introduced cjs build alongside (not bundled, unlike other Foundation projects)
- Drop dapjs fork (on GitHub) by adding import workaround until they have exports support (which we can do a PR for soon)
- Reluctantly use node10 module resolution to sidestep an issue with nrf-intel-hex (likely also fixed by introducing exports there)
- Using NodeNext with `type: module` in this package causes the ESM build to fail with errors about MemoryMap being a namespace not a type. I think this is what the `MemoryMap.default` cludges we've had to remove were addressing.
- I still don't entirely understand it. If you hack in `type: module` and the obvious `exports` into `nrf-intel-hex` then it builds cleanly so I think that's the best route forward but we'll need this in the interim.
We've verified that the built package can be consumed by our Vite builds, Vitest tests (which use Node) and a Webpack 5 project that mirrors code.org's configuration.
Because this cjs build depends on nrf-intel-hex we're also going to modernise microbit-fs to have a CJS build that doesn't bundle nrf-intel-hex.
0 commit comments