Failed to parse SourceMap

Question

Failed to parse SourceMap

Closed this issue 7 years ago · 8 comments

PolGuixe commented 8 years ago

I am getting this error in Chrome console with a package I made with this boilerplate: Failed to parse SourceMap.

But the map is under the /dist folder.

Answer 1 · 2016-07-18T15:39:33.000Z

Is the repo open source? If so, can you post a link to it?

Did you make any changes to the Gulpfile? What version of the boilerplate are you using?

Provide as much info as you can and I'd be happy to help out :)

Answer 2 · 2016-07-18T19:20:32.000Z

Any chance this is related to: webpack/webpack#2145

Answer 3 · 2016-07-18T19:30:27.000Z

Good find, @paulfalgout. Definitely seems like it could be related.

@PolGuixe are you using Chrome?

Answer 4 · 2016-07-18T21:43:31.000Z

@jmeas the repo is this one:
https://github.com/Zetoff/zetoff-three

I haven't made any changes to the gulpfile, I just added my source code and then ignored the /dist folder in the .gitignore file.

Answer 5 · 2016-07-18T22:04:25.000Z

@paulfalgout, @jmeas yes I am using Chrome and the issue is probably related to it. I don't see the same error in Safari.

And I am using Meteor as a build tool.

Is any of you experiencing a similar issue?

Answer 6 · 2016-07-18T23:15:41.000Z

Thanks for the update, @PolGuixe ! I'll check out the project later.

Is any of you experiencing a similar issue?

Tbqh I started a new job and haven't used the modules I've made (which are mostly for projects at my old job), so it's been some time since I've been consuming libs built by this boilerplate. I have a few ideas in mind for modules that I plan to build and start using soon, but I haven't yet done it.

So to answer your question, nope : [

Answer 7 · 2016-07-29T16:48:56.000Z

For future visitors, refer to the issue that @paulfalgout posted above. It seems that switching the source map option from eval to other options has helped some people.

I'll likely look into this soon to switch the boilerplate off of eval to one that works for me and some other test machines.

Answer 8 · 2017-07-06T01:29:30.000Z

Alright, I'm going to close this due to this recent comment: webpack/webpack#2145 (comment)

If anyone has further issues with this, refer to:

the above comments, which suggest some fixes
the linked webpack issue, which dives more into the root of the problem (it's a long issue...be warned)

If you think the issue is caused by this boilerplate specifically, leave a comment here and we can continue the discussion.