Skip to content
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

[vite] internal server error: buildings not found in WebContainers #118

Closed
FossPrime opened this issue Jun 10, 2023 · 5 comments
Closed

Comments

@FossPrime
Copy link

Pr workaround got merged... kat-tax/vslite#14

It would be great if upstream handled this for us. Ehum.

@FossPrime FossPrime changed the title [vite] internal server error: buildings not found in Web containers [vite] internal server error: buildings not found in WebContainers Jun 10, 2023
@ArnaudBarre
Copy link
Member

I'm not sure what you expect this package to do? Always download the babel version just in case you're running in web containers?

I think the long term fix is environment using a wasm build of SWC instead so that you can have the same behaviour (what Stackblitz does for esbuild I think).

For me this is not an issue. Babel is well more suited for demo/sandbox environment.

@FossPrime
Copy link
Author

Or how about doing an async import of the JS plugin?

That way if the user has it in his dependencies, it will just work without userland changes.

I would rather this had it as a devDependency... those are full of junk all the time... this would actually be helpful.

@ArnaudBarre
Copy link
Member

This will be very rare than the babel plugin is also installed. And then I have to be sure the options are compatible.

I think fixing it at the template level or in the repo for people using hybrid environnement is totally fine and doesn't sound like a hack that should be included in this plugin, juts a requirement (working in container environment) that is out of scope of this plugin for now

@FossPrime
Copy link
Author

FossPrime commented Jun 12, 2023

This will be very rare than the babel plugin is also installed. And then I have to be sure the options are compatible.

I think fixing it at the template level or in the repo for people using hybrid environnement is totally fine and doesn't sound like a hack that should be included in this plugin, juts a requirement (working in container environment) that is out of scope of this plugin for now

Providing a less arcane error message would also be extremely helpful. Perhaps one with a link to the workaround.

@ArnaudBarre ArnaudBarre reopened this Jun 12, 2023
@ArnaudBarre
Copy link
Member

Yeah something that I can do

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants