Open moos opened 6 years ago
Yes
n/a
node -v
npm -v
yarn --version
npm ls react-scripts
Then, specify:
Should have new copyright notice, e.g, from react-scripts' build.js
/**
It has the old (restrictive) copyright notice. Unfortunately these show up in the final *.map file which is public.
Build the app and check the content of the build/static/js/main.<hash>.js.map file
build/static/js/main.<hash>.js.map
Is this a bug report?
Yes
Can you also reproduce the problem with npm 4.x?
n/a
Which terms did you search for in User Guide?
n/a
Environment
node -v
:npm -v
:yarn --version
(if you use Yarn):npm ls react-scripts
(if you haven’t ejected):Then, specify:
n/a
Steps to Reproduce
n/a
Expected Behavior
Should have new copyright notice, e.g, from react-scripts' build.js
/**
Actual Behavior
It has the old (restrictive) copyright notice. Unfortunately these show up in the final *.map file which is public.
/**
Reproducible Demo
Build the app and check the content of the
build/static/js/main.<hash>.js.map
file