This is because npm started issuing additional messages to STDOUT that were not detected by netpack as warnings, and were therefore interpreted as errors.
"npm notice created a lockfile as package-lock.json. You should commit this file."
"npm ERR! extraneous: typescript@1.8.10"
NetPack detects these as errors because they don't start with WARN like other other warnings that npm writes to STDOUT.
Need to make Netpack handle this additional output and treat it as a warning.
NetPack processors can dynamically install
npmpackage dependencies that they need. However, this npm install process started failing recently during test runs on the build server: https://ci.appveyor.com/project/dazinator/netpack/build/0.2.0-alpha0009+59/testsThis is because npm started issuing additional messages to STDOUT that were not detected by netpack as warnings, and were therefore interpreted as errors.
"npm notice created a lockfile as package-lock.json. You should commit this file." "npm ERR! extraneous: typescript@1.8.10"
NetPack detects these as errors because they don't start with
WARNlike other other warnings that npm writes to STDOUT.Need to make Netpack handle this additional output and treat it as a warning.