Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Cannot split a chunk that has already been edited
See original GitHub issueGetting this as a warning in test suite.
Cannot split a chunk that has already been edited (0:87 – "from "/__NUXT_BASE__/@vite/client"")
reported by @pi0
Issue Analytics
- State:
- Created a year ago
- Reactions:9
- Comments:17 (6 by maintainers)
Top Results From Across the Web
Dynamic Import - Error: Cannot split a chunk that has already ...
The thing is the actual issue is that if a dynamic import is chunked together with another module that imports it as well...
Read more >Split chunk at the end of file when patching a file
The first thing to try is Michael Turczyn's solution: git add --patch filename . When you get to the final hunk, try s...
Read more >[Solved] Cannot split a chunk that has already been edited on ...
maia Asks: Cannot split a chunk that has already been edited on nuxt/tailwind project i have a nuxt3 project, and im using tailwind, ......
Read more >Code Splitting - SurviveJS
js is your split point. Examining the file reveals webpack has processed the code. If you want to adjust the name of the...
Read more >API - esbuild
API. The API can be accessed in one of three ways: on the command line, in JavaScript, and in Go. The concepts and...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Updating to
Nuxt CLI v3.0.0-27480141.51f3bbffixed it. Thanks. ❤️👍It’s not an issue with nuxi; you’ll need to update nuxt itself with
npx nuxi upgrade. And the package with the update was still going through CI at the time. (For reference, it is3.0.0-27480141.51f3bbf.)