To be able to remove this dependency, we must first publish compiled JS files that are Node.js "native" compliant, which is not the case today because the import statements don't have .js extensions (among other issues).
[ ] upgrade to the latest typescript version that require the minimum of changes in the codebase (probably 4.9)
[ ] for each package:
[ ] either add .js to TypeScript imports or use a bundler like microbundle or tsup
[ ] refactor tsconfig.json configs
Special case for the web package first needs some refactoring to be able to output compliant code:
[ ] dissociate the code that wraps Next.js calls of the Next.js codebase itself
[ ] extract the code shared between the 2 codebases to the core package (or other)
[ ] separate the two codebases
[ ] make two distinct build commands
[ ] reset the Next.js tsconfig.json
[ ] maybe stop doing an initial next build because not useful anymore?
Blocks https://github.com/thomvaill/log4brains/issues/135 (because of https://github.com/standard-things/esm/issues/931)
To be able to remove this dependency, we must first publish compiled JS files that are Node.js "native" compliant, which is not the case today because the
importstatements don't have.jsextensions (among other issues)..jsto TypeScript imports or use a bundler like microbundle or tsuptsconfig.jsonconfigsSpecial case for the
webpackage first needs some refactoring to be able to output compliant code:corepackage (or other)tsconfig.jsonnext buildbecause not useful anymore?