Comments (3)
mrm007
commented on August 21, 2024
Hi @Katsukiniwa, thanks for reporting this.
It sounds like it's related to the latest fix we did for the Webpack plugin in #1247.
from vanilla-extract.
Katsukiniwa
commented on August 21, 2024
@mrm007
Thanks!
However, I do not understand the modified PR that you taught me due to my lack of technical skills, and it appears difficult to resolve this issue on my own.
Is it possible for one of the maintainers to handle this issue?
from vanilla-extract.
mrm007
commented on August 21, 2024
@Katsukiniwa sorry, I didn't mean to say the solution is in the linked PR. Just a note to self and for @askoufis, who recently worked on that part of the codebase.
from vanilla-extract.
Related Issues (20)
- [VITE] Libraries shipping vanilla extract css loaded out of order when using vite HOT 1
- Next.js: Styles not loading after navigation with mixed pages/app HOT 3
- Error when updating Next.js to 14.2.2 version while using lodash-es in a @vanilla-extract/css file HOT 2
- Doesn't work since v4 HOT 2
- vite plugin fails to resolve files when full path starts with `/app` (remix, docker)
- 4.x breaks vite pre-rendering HOT 1
- Multline strings + webpack + storybook gives syntax error HOT 5
- @vanilla-extract/[email protected] hangs Vite build HOT 5
- Bad Error message when trying to use props values as Css values HOT 7
- error TypeError [ERR_INVALID_URL]: Invalid URL HOT 1
- When using "globalStyle" with "layer" styles are missing from generated css output if the same selector is used multiple times HOT 1
- New vite compiler cache skips adapter registration HOT 7
- Vite plugin not detecting changes for .css.ts files imported by other .css.ts files HOT 3
- Error when using Vanilla Extract Design system in a Turborepo monorepo with Next.js14 HOT 6
- When using Vanilla-extract with Turborepo and Next.js 14, a ModuleParseError occurs. HOT 7
- composedClassLists order completely wrong on new Vite compiler HOT 1
- Inconsistencies in classname between server and client builds HOT 1
- Recipe's runtime functions do not accept `undefined` as valid values for variants at the type level (`exactOptionalPropertyTypes`) HOT 1
- TS error with @vanilla-extract/sprinkles and pnpm mono repo.
- "module is not defined" in cssesc HOT 8
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 vanilla-extract.