BUG | Unable to start with npm about plasmo

[ColdSauce]

I'm going to close this issue for now, but please let me know if you think my assessment of the situation is incorrect, or if you have an up-to-date version of the graceful-fs package.

We'll think more about how to detect these npm cache issues on our side, but they might be outside Plasmo's scope.

[peterbe]

Switching to pnpm dlx plasmo init worked.

[ColdSauce]

Thanks for the bug report, @peterbe.

npm x plasmo init works both in our CI environment and locally on my laptop, so I suspect there is some weird cache issue happening here.

It seems to be an issue with the graceful-fs package that was fixed a while ago. We use this package because fs-extra depends on it:

λ ~/plasmo/plasmo/ main pnpm why graceful-fs
Legend: production dependency, optional only, dev only

p1asm0 /Users/coldsauce/plasmo/plasmo

devDependencies:
fs-extra 10.1.0
├── graceful-fs 4.2.10
└─┬ jsonfile 6.1.0
  └── graceful-fs 4.2.10

I suspect the problem is that your cached version of graceful-fs seems to be very old, and that's what's being used by npm x for some reason.

If you run

cat /usr/local/lib/node_modules/pnpm/lib/node_modules/npm/node_modules/graceful-fs/package.json | grep version

What version number does it show?