This message was deleted.

sparse-intern-71089

01/22/2019, 8:28 PM

This message was deleted.

white-balloon-205

01/22/2019, 8:29 PM

Did you import

@pulumi/pulumi

at the new version?

bitter-island-28909

01/22/2019, 8:29 PM

I did it like so:

const pulumi = require("@pulumi/pulumi");

bitter-island-28909

01/22/2019, 8:29 PM

sorry, my weak JavaScript might be betraying me

bitter-island-28909

01/22/2019, 8:30 PM

package.json has pulumi defined to be “latest”

white-balloon-205

01/22/2019, 8:30 PM

What version is in your package-lock.json?

bitter-island-28909

01/22/2019, 8:30 PM

aha, 0.12.1

bitter-island-28909

01/22/2019, 8:30 PM

thanks

bitter-island-28909

01/22/2019, 8:31 PM

sorry, should have thought of that myself. Got the commandline version conflated with the lib version

white-balloon-205

01/22/2019, 8:31 PM

Yeah - unfortunately we currently ship those together, which makes it a little less clear that they are versioned independently for users.

bitter-island-28909

01/22/2019, 8:45 PM

Ok I am very sorry to be a bother, but I can’t figure out how to make it upgrade. Specifying the new version in

package.json

and then running

npm install

gives:

Copy code

npm WARN registry Using stale data from <https://npmjs.pulumi.com/> because the host is inaccessible -- are you offline?
npm WARN registry Using stale package data from <https://npmjs.pulumi.com/> due to a request error during revalidation.
npm ERR! code ETARGET
npm ERR! notarget No matching version found for @pulumi/pulumi@0.16.11

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.