handle node_modules paths, and use module name instead of relative path #13
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.
Assume we have
and in
tsconfig-esm.json
and in
tsconfig-cjs.json
In that case, it should resolve as
awesomeModule/dist/cjs/index.js
andawesomeModule/dist/esm/index.js
respectively. But currently, it resolved as relative paths, and fails, asimport
statement made from source code, and now it's indist
folder, which make relative paths broken, e.g.Error: Cannot find module <PATH>/dist/node_modules/awesomeModule/dist/esm/index.js
.