-
-
Notifications
You must be signed in to change notification settings - Fork 150
Error: Multiple conflicting contents for sourcemap source. #238
Comments
It seems could be fixed by using old version(4.2.0) of rollup-plugin-vue. |
Thank you so much for sharing the solution! Hope this will be fixed in future releases. |
+1 Ran into this issue as well. I don't get this issue in all circumstances, but files that are nested in imports seem to cause an issue. If I get time I will try to see what could be causing this by comparing the code changes from 4.2. I will say, it's really hard to not just rollback to older versions. I had zero issues with other builds. It's been a real struggle just to update my dev dependencies and get stuff that has been working for a year to build correctly. Hopefully i get some time to look into this if someone else can't fix this. |
Is there an update on this issue? Watching is currently not possible if source maps are enabled. |
I have the same problem.This problem occurred when I used the 'router-link' tag to open a routing address with parameters. |
I have the same problem when save the vue file |
same here with |
@r4fx My projects are currently using rollup 0.65.0 and rollup-plugin-vue 4.2.0. Not sure if this could be a work around. Here are the devDependencies of one of my projects: "devDependencies": { |
See vuejs/rollup-plugin-vue#238 In this case, Rollup throws a hard error and aborts. This is highly disruptive for all that the issue when skipping would be a missing or corrupt sourcemap! Instead, let's just skip this particular iteration. It's not the prettiest workaround, but it does have the benefit of actually making us productive again. Woo!
See vuejs/rollup-plugin-vue#238 In this case, Rollup throws a hard error and aborts. This is highly disruptive for all that the issue when skipping would be a missing or corrupt sourcemap! Instead, let's just skip this particular iteration. It's not the prettiest workaround, but it does have the benefit of actually making us productive again. Woo!
Any news on this? This has been open for a while now and it's a fairly major issue during development. Quick fix for anyone looking to solve the issue npm i [email protected] |
Just ran into this as well. Seems to be some interaction with rollup-plugin-replace |
rolling back to v4.2.0 solves the problem. However, we need the latest version that solves other previous bugs. Can you tell us (or do you know) when this issue will be a priority to fix? |
Almost a year has passed since the issue was created. Milestone is version 4.7, but the latest version is 5.0.1. Everything looks like there will never be a solution 😔 |
Hi, I will donate $200 in BTC to whoever gets a perfect fix* to this problem merged into rollup/rollup-plugin-vue. Offer expires in 1 month (September 16th, 2019). *as in: no hacks. |
Not a "fix" but a plausible solution was committed in 3f879f3 It seems it has to do with how rollup's
I am using TypeScript and haven't found issues with the source maps even after adding |
Similar to #248, tracking there. |
FYI: @darionco 's fix worked for me. |
@darionco 's fix worked for me too. rollup-plugin-vue 5.1.6 |
@darionco Your solution works for me, but what does |
I dug through the code back when I posted this solution, I can't remember what it does anymore but it is safe to use and it does NOT disable source maps... Maybe @znck remembers what it does? (he implemented it) |
needMap generates source maps for script block. |
@znck So by setting |
Yep. |
But in additional it generates virtual js files, that contain only js code of component and it are debugable. Without But in this case I can't use import {watch} from "rollup";
import {inputOptions, outputOptions} from "./my-options.js";
const watchOptions = {
...inputOptions,
watch: {
skipWrite: true,
}
};
const watcher = watch(watchOptions);
watcher.on("event", async event => {
if (event.code === "BUNDLE_END") {
const res = await event.result.generate(outputOptions); // Error (after I changed a watched file)
}
}); |
And it forces me to use the full Rollup rebuilding: watcher.on("event", async event => {
if (event.code === "START") {
await build();
}
}); What takes noticeable additional time. |
I think this issue should be reopen. #248 is about the related bug to this one, but it is not the same bug. Currently it's impossible to use const outputOptions = {
sourcemap: true
}; Because you will get (v5.1.9) *And for |
This poll request (not accepted) fixes this issue. But it applies only on 6.0.0. version of this plugin that works only with Vue 3.0. Also I can note that Is it a bug? How to disable it? |
This bug should be reopened. It is still an issue with v6.0.0 and it is not the same bug as #248. It prevents using watch mode when source maps are needed. |
…ltiple conflicting contents for sourcemap source" — according to this link I added needMap: false, to the vue rollup plugin, so I get the error but the page reloads now and it breaks sourcemaps for SFCs. vuejs/rollup-plugin-vue#238. Might be able to do better than this? Not sure.
Hi.
I was trying to use rollup to build a simple vue app. But an error occur every time I changed the style of a component.
I don't know how to fix it. Here is the project file: rollup-issue.zip
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: