Installations

npm install smart-source-map-loader

Pull Requests

Open

1

Total

21

Closed

20

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Developer

AlexanderOMara

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

>=6.11.5

Typescript Support

No

Node Version

20.16.0

NPM Version

10.8.1 Statistics

6 Stars

214 Commits

1 Forks

3 Watching

2 Branches

1 Contributors

Updated on 05 Aug 2024

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

70,378

Last day

-37.8%

79

Compared to previous day

Last week

-1.5%

526

Compared to previous week

Last month

13%

2,259

Compared to previous month

Last year

-24.9%

17,974

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

1

loader-utils

Peer Dependencies

1

webpack

Dev Dependencies

14

@babel/cli @babel/core @babel/preset-env @eslint/js @stylistic/eslint-plugin babel-plugin-search-and-replace eslint eslint-config-prettier eslint-plugin-jsdoc memory-fs node-require-function prettier rimraf source-map-support

Versions

Smart Source Map Loader

A Smart Source Map Loader for Webpack

Overview

This is a module which will read any existing source maps on a file and pass them to Webpack. In this way compiled code can be bundled with source maps to the original source files.

It is similar in concept to the source-map-loader module, but with several major usability improvements. These improvements mainly center around the issue where that module does not correctly resolve the original source paths in most cases, leading to conflicting or wrong paths in the resulting source maps. In order to solve these and several other minor issues, a smarter loader had to be written, and so this loader was created.

Features

Correctly resolves the path of the original source files relative to the source maps to avoid conflicts and wrong paths in the resulting bundle.
Only accepts well-formed source map comments (with one exception for path encoding) at the end of the file (other comments are almost always extraneous).
Handles both spec-compliant encoded and unencoded comment paths (for compatibility with the rest of the ecosystem, typically a non-issue).
Correctly handles external and data URI source maps.
Correctly handles the indexed format and reading source contents from disk when needed.
Avoids adding absolute paths where possible.
Strong error handling to produce helpful warning messages when a source map is invalid.
Well-tested against the real Webpack module.

Usage

Requires Webpack 4+.

Just add the dependency with npm:

1npm i -D smart-source-map-loader

Or yarn:

1yarn add -D smart-source-map-loader

And configure it to parse your source files (.js and .mjs in this example):

1module.exports = {
2	module: {
3		rules: [
4			{
5				test: /\.m?js$/i,
6				use: ['smart-source-map-loader'],
7				enforce: 'pre'
8			}
9		]
10	}
11};

For performance reasons you may wish to exclude node_modules in your setup.

If you do include them though they will have the correct path in the source map.

Bugs

If you find a bug or have compatibility issues, please open a ticket under issues section for this repository.

License

Licensed under the Mozilla Public License, v. 2.0.

If this license does not work for you, feel free to contact me.

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

3

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

Maintained

Determines if the project is "actively maintained".

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

SAST

Determines if the project uses static code analysis.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

2.7

/10

Last Scanned on 2024-11-25

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More