-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Broken in Vite 5 #129
Comments
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as off-topic.
This comment was marked as off-topic.
vite-tsconfig-paths v3.6.0 downgrades will normal operation. |
I could not reproduce with the given StackBlitz, @tervay. I also tried reproducing manually, but no luck. Please try clearing your node_modules, deleting your lockfile, and re-installing to see if that fixes it for you. Otherwise, please provide a proper reproduction, thanks. |
@aleclarson The stackblitz will fail when running |
I'm having the same issue. It fails only when used as a worker plugin. Just like in the provided StackBlitz.
|
The error happens at this line: vite-tsconfig-paths/src/index.ts Line 164 in dd3fc7e
My insight on this is that vite-tsconfig-paths/src/index.ts Line 125 in dd3fc7e
undefined .
I was able to workaround it by passing the same plugin object to both arrays, since it uses the same tsconfig for workers and main project. That way the const tspaths = tsconfigPaths()
export default defineConfig({
plugins: [tspaths],
worker { plugins: () => [tspaths] },
}) |
Closing this. The Vite PR has been merged. Not sure what the release schedule is these days. If you have any other problems with Vite 5 and this plugin, open a new issue. |
https://stackblitz.com/edit/vitejs-vite-2pijh9?file=package.json
This stackblitz resembles a project structure I'm using that no longer works with Vite 5. In Vite 4, this project will (intentionally, in this Stackblitz case) fail due to a top-level await not being allowed in the configured environment (which is fine, expected, and desired in this case).
With Vite 5.0.2, this fails with the following stack trace:
I'm not familiar enough with Vite to further debug this.
The text was updated successfully, but these errors were encountered: