Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot split a chunk that has already been edited (Watch API only) #4415

Closed
haseebanwar opened this issue Feb 21, 2022 · 6 comments · Fixed by #4589
Closed

Cannot split a chunk that has already been edited (Watch API only) #4415

haseebanwar opened this issue Feb 21, 2022 · 6 comments · Fixed by #4589

Comments

@haseebanwar
Copy link

haseebanwar commented Feb 21, 2022

Rollup Version

2.67.3

Operating System (or Browser)

Windows

Node Version (if applicable)

16

Link To Reproduction

https://github.com/haseebanwar/rollup-issue
After cloning the repo, if you run

npm run build

It will work fine but if you run

npm start

You will see the error

Expected Behaviour

It bundles

Actual Behaviour

It doesn't bundle

I am using rollup-plugin-terser as an output plugin. Not sure if this is an error from rollup or the terser plugin. The reason I am creating an issue here first is that rollup only throws this error when I use the watch API. It works fine with rollup.rollup function.

#2660 and #2676 looks familiar

@haseebanwar
Copy link
Author

Excuse me if I am asking too early, but do we have any updates on this? This is stopping a very crucial function of our build tool. I am also trying to figure out the issue myself but no leads now.

@lukastaegert
Copy link
Member

This error is usually generated by magicstring, which is responsible for generating sourcemaps in Rollup and some other plugins. Did not find time to look into this, though.

@haseebanwar
Copy link
Author

I hope someone will pick it soon

@danielbayerlein
Copy link

@haseebanwar
Copy link
Author

Hi @lukastaegert, were you able to look into this?

Thanks

@lukastaegert
Copy link
Member

We finally have a fix for this at #4589

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants