Comments (4)
I got a bunch of reports of that exact error in 2.3.6 and they said they needed to lock at 2.3.4. This was supposed to fix that. By removing the .jsx and .tsx like we did previously it was supposed to not send the JSX to the optimizer which means ESBuild shouldn't be getting it which should avoid the error.
Are you exporting JSX without a JSX extension. That's the only reason I can think of it getting to ESBuild.
from vite-plugin-solid.
Alright.. That's interesting. 2.3.6 happened to be the only version we've ever released that would have worked for the way the library is configured. Generally "solid" field expects a .jsx extension if it contains JSX. I think I have a middleground fix. But ultimately this is an issue I need to take up with Vite. There is just weirdness going on that is forcing us to jump through these hoops.
Published in 2.3.8.
from vite-plugin-solid.
Thank you so much for the comprehensive explanation here. Now I know what is going wrong 😅 I'll push for a new release that follows the best practice here by exporting index.jsx. Thanks again for jumping on it so fast.
from vite-plugin-solid.
v2.3.8 indeed fixed the issue. I will close this issue for now. Thanks again
from vite-plugin-solid.
Related Issues (20)
- Upgrade compatibility with Vite 5 HOT 3
- alias normalization breaks config
- Not working with happy-dom
- 2.8.1 vite dev server : Uncaught ReferenceError: _tmpl$ is not defined HOT 6
- Interpolation syntax error causes unhelpful "Invalid raw" error
- scope.registerDeclaration(declarationPath) error with vite-plugin-solid 2.8.2 HOT 6
- peerDependencyMeta in package.json should be peerDependenciesMeta
- vite-plugin-solid v2.8.3+ causes: `TypeError: Cannot read properties of undefined (reading 'extend')` HOT 1
- missing changelog / release tags HOT 1
- optimizeDeps.include will produce the React version of the jsx result HOT 1
- I updated `vite-plugin-solid` and now namespaces merged with components are no longer allowed HOT 11
- Unable to pass signal to child components HOT 5
- Breaking updating from v2.9.1 from v2.10.0 HOT 1
- Should omitNestedClosingTags be actually required? HOT 1
- HMR not work in "solid-ts" template HOT 1
- Vite does not load proper build (server) on ssr webworker build HOT 5
- feature: SWC support
- Put packge into `@solidjs` namespace
- Vitest fails with TypeError: Unknown file extension ".jsx" HOT 5
- [vite] server connection lost. Polling for restart...
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vite-plugin-solid.