Today I Learned - Rocky Kev

TIL avoiding including Sourcemaps

POSTED ON:

TAGS: compression performance buildtools

Sourcemaps are great.

  1. It allows us to minify/obfuscate files so we send smaller files to users.
  2. It maps where each spot was 'minified', so developers can quickly debug issues in our non-minified code.

One mistake I see developers do is include the Sourcemaps in their production files by bundling the two together.

On the technical side - Sourcemaps are a base64 representation of the original source into a production-ready JavaScript asset.

Inlining source maps means that you’re not just sending your JavaScript resources to users, but also their source maps, which can lead to oversized JavaScript assets that take longer to download and process.

via Part I Chapter 2 JavaScript

Keep them separate. And in the build tools, separate it so production builds don't even create sourcemaps.

Related TILs

Tagged: compression

TIL avoiding including Sourcemaps

Sourcemaps are a base64 representation of the original source into a production-ready JavaScript asset.

TIL unzipping a file in node using zlib

Since my application needs to read whatever is inside that '.gz' file, I had to figure out a way to simplify that. That was done with zlib.

TIL unzipping a file in node using zlib

Since my application needs to read whatever is inside that '.gz' file, I had to figure out a way to simplify that. That was done with zlib.