fix: use internal node_modules for remapped files #1949
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Avoids issues with nested package.json resolution which is finicky in several tools (including vitest and jest).
The fix here is somewhat of a hack but appears to work in all supported environments. The hack is to move all of these remapped files into their own
node_module
package folder that comes with the Marko runtime (seepackages/marko/src/node_modules/@internal
).Checklist: