This message was deleted.

sparse-intern-71089

11/08/2019, 1:41 PM

This message was deleted.

stocky-island-3676

11/08/2019, 1:42 PM

Use-case: I’ve changed sth. to

pulumi-kubernetes

where the module resides in the

sdk/nodejs

subdirectory. Locally it works fine with

npm install ../github.com/pulumi/pulumi-kubernetes/sdk/nodejs

. But now I want to make it accessible for other before my (possible) contribution (may) get merged & released upstream. Therefore I want to deliver the changes in a company-internal fork. Then I get to the problem above:

npm ERR! Error while executing:

npm ERR! /usr/local/bin/git ls-remote -h -t git://github.com/ORG/pulumi-kubernetes/sdk/nodejs

npm ERR!

npm ERR! fatal: remote error:

npm ERR! ORG/pulumi-kubernetes/sdk/nodejs is not a valid repository name

npm ERR! Email support@github.com for help

future-barista-68134

11/11/2019, 5:41 PM

Could you publish the package to an internal repo or private npm org? Note: you would have to update the name and version. Also, you could create another repo that includes just the code in the nodejs folder at the root and it should work since node assumes that the package is at the root.

stocky-island-3676

11/13/2019, 8:14 PM

@future-barista-68134 I wanted to keep it as simple as possible. Didn’t publish to npm.org by myself. I might move the

./sdk/nodejs

folder to root in the fork. That way I hopefully can synch with upstream.

👍 1

4 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.