question-mark
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.

Sourcemap from bundle is not utf-8 encoded

See original GitHub issue

This can be seen in sourcemap

image

This is the actual bundle generated

image

The letter å is wrong. Not sure if it’s Webpack’s fault or Sourcemap’s?

Using Linux if that matters. Using devtool: '#source-map'

This is a letter only used in comments, not actual source, so shouldn’t be a real problem.

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Reactions:3
  • Comments:18 (9 by maintainers)

github_iconTop GitHub Comments

3reactions
paul-sachscommented, Aug 14, 2017

Also running into this. Doesn’t seem to be any pattern, i have files either encoded as utf-8 or us-ascii.

0.e6063d8a791459c43093.chunk.js.map:                 text/plain; charset=us-ascii
1.e6063d8a791459c43093.chunk.js.map:                 text/plain; charset=utf-8
10.e6063d8a791459c43093.chunk.js.map:                text/plain; charset=utf-8
11.e6063d8a791459c43093.chunk.js.map:                text/plain; charset=utf-8
12.e6063d8a791459c43093.chunk.js.map:                text/plain; charset=utf-8
13.e6063d8a791459c43093.chunk.js.map:                text/plain; charset=utf-8
14.e6063d8a791459c43093.chunk.js.map:                text/plain; charset=utf-8
15.e6063d8a791459c43093.chunk.js.map:                text/plain; charset=utf-8
16.e6063d8a791459c43093.chunk.js.map:                text/plain; charset=us-ascii

In fact, this is not limited to source maps. My bundles are also scattered, some utf-8, some us-ascii. I’d like them to all be utf-8 encoded. Can this be forced? I tried webpack-encoding-plugin but it didn’t work.

Using webpack 3.2

0reactions
webpack-botcommented, Feb 27, 2019

Issue was closed because of inactivity.

If you think this is still a valid issue, please file a new issue with additional information.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Unicode characters not showed when bundling and deploying ...
On my local environment, unicode characters work fine but when I run webpack to bundle and deploy, string which is like "\uf00c" becomes ......
Read more >
Source map not in utf8 encoding - #sentry
Sentry reports that our source file was not utf8. Uploading the map directly to Sentry with the API works fine.
Read more >
Source Maps from top to bottom - ITNEXT
This article covers a basic overview and an in-depth explanation of the mechanics of JS code generators and source maps.
Read more >
webpack character encoding - Medium
The problem only happens when using webpack's -p plus the cheap-module-source-map option. I'm not sure exactly where the problem lies, but since it...
Read more >
Source Maps | webpack surviveJS - GitHub Pages
It's possible you don't want to generate a source map for your production bundle as this makes it effortless to inspect your application....
Read more >

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Hashnode Post

No results found