Closed joseph-cloudthing closed 6 years ago
by design
This is because I don't have the .js source checked in, I'm using TypeScript. If you run "npm build" (and you might need to run "npm install" again to include my dev dependencies), then it would generate the .js output when you install from JS.
I could theoretically have a "install" script which would detect if the .js source is installed and then install it. Not sure if that's a common pattern.
Question: Why are you trying to npm install from github and not NPM?
Hey @christopheranderson I was just hoping to install azure-functions-pack from a branch quickly to test possible fixes. Checking out building/installing isn't a deal breaker, was just annoying :)
Don't worry about closing if it's not important!
It's not so much that it's not important. It's that I don't want to check in generated files, I feel that that is generally a bad practice.
The work to make installing from github isn't trivial, so if you don't mind, I'll just close this as won't fix for now. Thanks.
Definitely makes perfect sense.
From the registry, all fine:
From any other possible location, I get a failure at the same point. e.g. git:
This is the same when pointing at tar.gz's etc.
I'm new to node, but I'm not having this issue when installing from git or tar.gz with any other package I try.