-
Notifications
You must be signed in to change notification settings - Fork 136
Breaking change for file paths in recent npm compatibility update #477
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
How are you doing this in the first place? |
Maybe through |
Will try making a new release later today with |
I think you'll run into the same issue - I'll look into if there is anything we can do here to fix this |
@donovanglover We're going to update the emit to emit the |
Some relative specifiers were being incorrectly emitted when referencing a `.js` file from a `.d.ts` file in the dist folder. Additionally, `.js` files were previously emitted into a `_dist` folder, which broke users that need to relatively access files in the NPM package using `import.meta.url` or similar. Now only `.d.ts` files are emitted into the `_dist` folder. Fixes #491 Fixes #477
The recent PR #463 causes
__dirname
to include./_dist
, breaking packages that depend on files relative to__dirname
.For example,
join(__dirname, '../schemes')
will resolve to./schemes
in_jsr_revision
8 and./_dist/schemes
in 10.Related: #462
The text was updated successfully, but these errors were encountered: