You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that as of 1420d41#r28075777, VSCode no longer provides an install task by default in its npm extension, making setting up new projects less convenient when there is no install hook in package.json (which applies to most packages).
VSCode Version: 1.22.2 and 1.23.0-insider
OS Version: macOS 10.13.4
Steps to Reproduce:
Start a new project with a package.json file.
Add a test script.
Run Tasks: Run Build Task. Note that test is present, but install is not.
Add an install script.
Run Tasks: Run Build Task. Note that both install and test are present. VSCode now recognizes the built in install task because it thinks it's a custom script, when it's actually an npm install hook.
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered:
It appears that as of 1420d41#r28075777, VSCode no longer provides an
install
task by default in its npm extension, making setting up new projects less convenient when there is no install hook inpackage.json
(which applies to most packages).Steps to Reproduce:
package.json
file.Tasks: Run Build Task
. Note that test is present, but install is not.Tasks: Run Build Task
. Note that both install and test are present. VSCode now recognizes the built in install task because it thinks it's a custom script, when it's actually an npm install hook.Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: