Open moroshko opened 2 years ago
Experiencing this issue with nextjs12
Same here :(
Any updates here? I'm also having this issue with Next.js 14.1.1
I added identifiers: 'short'
In my next.config.js
:
const withVanillaExtract = createVanillaExtractPlugin({
identifiers: 'short',
});
it reduces the classnames string length and help to drastically reduce the build time (and serialized string size) Also, I noticed that removing conditions in sprinkles can help too
same in next v14
After some investigation, I have found that it is not related to vanilla extract at my side. Instead it is related to Mantine by adding the following to my
next.config.mjs
fixed my problem.experimental: { optimizePackageImports: ['@mantine/core', '@mantine/hooks'], },
this worked for me also
experimental: { optimizePackageImports: ['@mantine/core', '@mantine/hooks'], },
Thanks! This precisely fixed the same issue on my side! (NextJS + Mantine)
same in next v14
After some investigation, I have found that it is not related to vanilla extract at my side. Instead it is related to Mantine by adding the following to my
next.config.mjs
fixed my problem.experimental: { optimizePackageImports: ['@mantine/core', '@mantine/hooks'], },
this worked for me also
Thank you so much. Fixed my issue
same in next v14
After some investigation, I have found that it is not related to vanilla extract at my side. Instead it is related to Mantine by adding the following to my
next.config.mjs
fixed my problem.experimental: { optimizePackageImports: ['@mantine/core', '@mantine/hooks'], },
I have the same issue but I'm not using Mantine UI, how can I detect which package is causing this warning?
same in next v14
After some investigation, I have found that it is not related to vanilla extract at my side. Instead it is related to Mantine by adding the following to my
next.config.mjs
fixed my problem.experimental: { optimizePackageImports: ['@mantine/core', '@mantine/hooks'], },
This fixed it for me. Thanks!
Describe the bug
Strangely enough, adding more sprinkles (see this commit) causing the following warning to appear in Node's console:
Link to reproduction
git clone https://github.com/moroshko/webpack-cache-issue.git
cd webpack-cache-issue
yarn
yarn dev
Note: You might need to
rm -rf .next
to see the warning.System Info