Open TessavWalstijn opened 1 year ago
Latest commit: 2eafb739f515b0f4b096a162062f34fda77fa9d2
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
Hm, having used vite myself, I have not experience such an issue. Could you share your project or a minimal reproduction so that I can understand what's happening here?
Hm, having used vite myself, I have not experience such an issue. Could you share your project or a minimal reproduction so that I can understand what's happening here?
Sure I will try to reproduce the issue.
Oh, I came back here looking at some other PRs and I think I realise that your problem is probably with TS module resolution.
I think a more robust improvement would be to add .js
extension to imports/exports
Cool!
Sorry haven't come around it to create a simple way to reproduce my issue.
I might be able to spend some time to try your solution with the next upgrade cycle.
Sorry haven't come around it to create a simple way to reproduce my issue.
So, expanding on my comment above, I expect you should be able to reproduce when you set moduleResolution
to Node16
or NodeNext
.
Hi hi so I was able to create a minimal reproduction: https://github.com/TessavWalstijn/vue2-ts.rdfjs-types-issue
Switching moduleResolution to:
Node10
originalNode16
NodeNext
Did not resolve the issue.
Moving from Webpack 4 to Vite 4.
When we build our application we get the error that Vite:
I was able to solve the issue locally by editing the
index.d.ts
from this package.I hope with this change to make rdfjs accessible for Vite users as well.