Support isolated packages
(a requirement to get types passing)
Previously, everything was all loosey goosey / incorrect.
@glimmer/runtime was not specified, adding it adds the ESM version of Glimmer. No modern version of @glimmer/* exports CJS, and thus is not compatible with Glint (which is compiled to CJS (because VSCode extensions don't support ESM))
@glint/core was added to any package that invokes the glint bin. This is required, because bin directories are are local to each package.
Other glint packages were added to each package that imports from them, because there is no more hoisting, which means TS can't find the packages unless they are declared in the package.json. This has been done as devDependencies
We can't have dependencies loosely importing from all over the place, so extra packages have been extracted for integration testing
Example: @glint/corecannot have tests that consume any environment package, because the environment packages depend on @glint/core
There are resolution issues with the environments. :(
yarn@v1
can't be trusted. this has been known for ages. Also, newer tooling isn't supportingyarn@v1
.unblocks: https://github.com/typed-ember/glint/pull/668
Changes:
@glimmer/runtime
was not specified, adding it adds the ESM version of Glimmer. No modern version of@glimmer/*
exports CJS, and thus is not compatible with Glint (which is compiled to CJS (because VSCode extensions don't support ESM))@glint/core
was added to any package that invokes theglint
bin. This is required, becausebin
directories are are local to each package.devDependencies
@glint/core
cannot have tests that consume any environment package, because the environment packages depend on@glint/core