terser/terser

Recommend --enable-source-maps

Open

#732 opened on Jun 14, 2020

View on GitHub
 (0 comments) (2 reactions) (0 assignees)JavaScript (8,215 stars) (386 forks)batch import
good first issue

Description

Bug report or Feature request? Feature request (docs)

Version (complete output of terser -V or specific git commit) any

Complete CLI command or minify() options used N/A

Because --enable-source-maps is now a thing, Terser's readme and issue template should recommend it. It should be a lot easier to use than installing and requiring source-map-support in code you don't really control. Using it as part of the NODE_OPTIONS environment variable is especially interesting, because it affects Terser even if it was invoked from a child process.

Contributor guide

Tech stack
javascriptnodejs
Domain
documentationdeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with Terser CLIBasic knowledge of Node.js source maps
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90
Research direction
Review the current README.md and issue template files in the repository. Identify where to add a recommendation for using enable source maps via NODE OPTIONS. Consider referencing the linked issue #680 for context. The change is a simple text addition.