i'm getting this ```npm ERR! Unexpected end of JSO...
# general
b
i'm getting this
Copy code
npm ERR! Unexpected end of JSON input while parsing near '...86668803","dependenci'
ever since 1.14.1 - in the debug log it prints
Copy code
345 http fetch GET 200 <https://registry.npmjs.org/@pulumi%2fpulumi> 38ms (from cache)
346 silly fetchPackageMetaData error for @pulumi/pulumi@^1.14.1 Unexpected end of JSON input while parsing near '...86668803","dependenci'
i've done
npm cache verify
and it's no better. not sure what else to try
@broad-dog-22463? any ideas?
b
is this from a new project or an upgrade?
b
upgrade
b
can you show me the contents of your package.json?
b
Copy code
"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"
    }
b
and what version of Pulumi did you upgrade from?
b
the CLI or the package?
b
package
b
1.10.1
b
and you just changed the version and ran npm install?
b
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
b
mmmhhhh so it feels like it almost got corrupted on download?
b
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 have no idea
b
so it seems like it's ok now?
b
yeah all working now thanks
b
phew!
I was worried we had a big problem 🙂
b
😄