Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Do not run npm install if generated package json content has not changed #6385

Merged
merged 2 commits into from
Sep 6, 2019
Merged

Do not run npm install if generated package json content has not changed #6385

merged 2 commits into from
Sep 6, 2019

Commits on Sep 3, 2019

  1. Do not run npm install if generated package json content has not changed 

    Stores hash of the generated package json file in the main package json
(inside node_modules, outside target folder) and updates it every time
when the generated content is changed. TaskUpdatePackages modified
status is changed only if the hash value is changed. It allows do not
run npm install even if the generated package.json file is regenerated.

Fixes #6151
    Denis Anisimov committed Sep 3, 2019
    Configuration menu
    Copy the full SHA
    1f7bc84 View commit details
    Browse the repository at this point in the history

Commits on Sep 6, 2019

  1. Remove sysouts.

    Denis Anisimov committed Sep 6, 2019
    Configuration menu
    Copy the full SHA
    d7df66f View commit details
    Browse the repository at this point in the history