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.

Pulumi Community

i've done `npm cache verify` and it's no better. not sure what else to try

is this from a new project or an upgrade?

can you show me the contents of your package.json?

```    "devDependencies": {
        "shx": "^0.3.2",
        "typescript": "^3.8.3",
        "@types/semver": "^7.1.0"
    },
    "dependencies": {
        "@azure/ms-rest-js": "1.8.13",
        "@pulumi/azure": "^2.4.1",
        "@pulumi/azuread": "^1.8.0",
        "@pulumi/kubernetes": "^1.6.0",
        "@pulumi/pulumi": "^1.14.1",
        "@pulumi/random": "^1.7.0",
        "ajv": "^6.12.0",
        "semver": "^7.3.0"
    }```

and what version of Pulumi did you upgrade from?

and you just changed the version and ran npm install?

well i'm referencing an internal package but 1.10.1 is what's in package-lock.json

lots of other projects referencing the same package worked fine but this one has gone crazy

hm i did `npm cache clean --force` and it's fine so obviously something at my end sorry about that

no idea how it can verify successfully if its corrupt though

mmmhhhh so it feels like it almost got corrupted on download?

yeah maybe verify only verifies the package itself not the cache of the response from npm registry?

and it was the manifest that was corrupt?

I was worried we had a big problem :slightly_smiling_face: