This repository has been archived by the owner on Sep 5, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
remove postinstall hook from package.json #987
Labels
Milestone
Comments
Jeez, what a mess, now I run into the following.
I do not want to use the mist nodes but the system wide nodes. Please, help a desperate package maintainer :-) I totally understand your motivation, you want it straight forward easy and simple for the end user. But for those who know their tools, please allow alternative paths! Thanks :-) Related: #264 |
Try now, this PR should solve your problem:
|
This was referenced Sep 26, 2016
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The package.json contains the following:
Which causes each
npm install
to trigger agulp update-nodes
after the installation. Took me a while to figure out where that came from.In the docs you describe the installation as follows:
Which describes the intentions of
npm install
andgulp update-notes
to be separated commands. As for now it is not possible to install mist without triggering a full download of all nodes for all operating systems (this is yet another issue).Please remove the postinstall hook from
package.json
or provide a convenient way of disabling theupdate-nodes
command. Also I would strongly recommend to only download the target OS version of the node.The text was updated successfully, but these errors were encountered: