Skip to content

Improving D2D mapping for npm - .map files #1859

@chinyeungli

Description

@chinyeungli

A .map file is typically a source map used in deployment environments to link compiled code back to its original source files.

It would be highly beneficial if the tool could analyze .map files and automatically resolve the paths listed in the "sources" section to verify their presence in the development codebase.

For example:
carbon-addons-iot-react.css.map

"sources": [
  "styles.scss"
]

Here, styles.scss should be flagged as mapped if found in the development codebase.

bundle.js.map

"sources": [
  "../src/queue.ts",
  "../node_modules/tslib/tslib.es6.js",
  "../src/error.ts",
  "../src/browser.ts",
  "../src/simple.ts",
  "../src/index.ts"
]

Each of these paths should be individually checked. If all are found, the .map file is considered fully mapped.
However, if any source file listed cannot be mapped, the .map file should be flagged as requires-review , indicating that manual review is needed to ensure source integrity.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions