Comments (8)
Hi,
Could you try this out?
module.exports = {
experimental: {
serverMinification: false,
....
},
....
}
And see if that helps out? Also, you have two next.config files, you probably want to drop one of them.
from next.js.
I removed the next.config.mjs
file (locally) and edited the next.config.js
file to be:
module.exports = {
// ... rest of the configuration.
output: "standalone",
experimental: {
serverMinification: false,
},
reactStrictMode: true,
};
It's still minifying from the looks of it as it's still changing the class names to o
and such (and thus makes it so the problem is still there). Is this dependent on a particular version of Next? (Mine's showing up as version 14.1.3)
Additional note: I tried the same thing but with using next.config.mjs
instead and the same issue. I also checked on 2 different browsers in case it was a cacheing issue and that didn't resolve the issue.
from next.js.
Turn off swcMinify too, that one is at the root of the config, not experimental
from next.js.
Here's the updated config:
module.exports = {
// ... rest of the configuration.
output: "standalone",
experimental: {
serverMinification: false,
},
reactStrictMode: true,
swcMinify: false,
};
Unfortunately still getting the same error =/ Again tried on a couple browsers and ran build twice just in case.
Just in case it is a cache thing: Do I need to delete old builds or by running npm run build
and then npm run start
that should automatically handle old build cleanups and such and only use the most recent build correct?
from next.js.
I don't know what you mean by default/name exports. You mean in the config file?
from next.js.
I wonder if you could try to set up a reproduction repository? like try to remove as much as possible from the business logic, and just keep the code that breaks
from next.js.
I tried to remove as much as I could. I'm still getting an error that more than 1 item is being called the same thing. The good thing is that now there's a lot less collisions, but there's still collisions.
To help separate things, I created a new branch:
https://github.com/thecaligarmo/ngu-idle-calculators/tree/test-next
from next.js.
As an update. using the serverMinification and the swcMinify did nothing, but adding the following:
webpack: (
config,
{ buildId, dev, isServer, defaultLoaders, nextRuntime, webpack }
) => {
config.optimization.minimize = false
return config
},
made it so minimization was no longer happening and everything is working again. I'm not sure if that means this is no longer a bug or not, but from the looks of other issues, this seems to creep up every so often, so not sure what the best fix is.
from next.js.
Related Issues (20)
- Getting redirected to the copied link unexpectedly. HOT 1
- Modal by parallel routing on slow connection not working. Clicking on Link before hydration causes full reload instead of showing modal HOT 1
- ChunkLoadError: Loading chunk app/layout failed. (timeout: http://localhost:3000/_next/static/chunks/app/layout.js)
- ISR: Cached 404 status never change even if page is not a not-found anymore HOT 1
- Suspense does not work with Next.js 15 RC and Vercel HOT 1
- Custom events don't work in custom elements
- Tailwindcss content when using src directory HOT 1
- Flask + NextJs works locally but Flask api do not work on Vercel
- OpenGraph ImageResponse doesn't render UTF-8 characters properly
- [Bug][v13.5]build with terser error(Unexpected token: punc ({))
- Polyfills for findLast and findLastIndex are missing
- Anchor download does not start a download
- CJS module package code that contains "typeof window === 'undefined'" checks are not excluded from app router client builds
- Test again.. HOT 5
- Issue with adding "alternates" in the sitemap
- Unable to build next js
- Next Build fails with Turborepo v2 and bun as package manarger HOT 1
- intercepting routes return 404
- Server Side Exception during Production while implementing pagination and reading from search params. Application error: a server-side exception has occurred (see the server logs for more information). Digest: 163034583 HOT 1
- Tailwindcss "content" when using src directory
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 next.js.