-
-
Notifications
You must be signed in to change notification settings - Fork 150
Error: Unsupported previous source map format: [object Object] #239
Comments
should be resolved in #243 |
So after testing this change, I am still getting the error. The error only happens however when I use --watch, and make a change to the CSS. This error use to occur when I made changed to parts of the template. The template never triggered a consistent error, and changes always ended up triggering the css. NOW, the CSS triggers an error after every single change but template seems fine. Steps to reproduce this behaviorUsing very similar config as above, but I have tested with only those plugins, I run
Note, I removed PostCSS, and copied index.ts from master and rebuilt and I still get this the following error. |
So a little more information on how to duplicate the above error, if I make a change to the file after running If I make the change again, I get the error. One thing I just noticed is when I make a change to the JS, then it recompiles the source map for the entire file and I don't get the error. I can make another CSS change and then get the error, change the JS and save, error goes away (and repeat). Summary: it seems like any change to the template and/or CSS will result in a conflict source map until the JS file has changed which recompiles the source. Im still trying to get a handle on Rollup plugin debugging and dev, so still can't find erroneous code, but this should help duplicate it. I will post back if I figure how which line of code is causing this. |
|
Similar to #248, tracking there. |
Expected behavior
No error
Actual behavior
Emitted error but outputs seems are correct.
Steps to reproduce the behavior
Using multiple rollup configs and extract css with
css: false
will emit this error on the second build.The text was updated successfully, but these errors were encountered: