Npm ERR! enoent ENOENT: no such file or directory, open 'C:\Users\anton\Desktop\Projects\TextAdventures\package.json' Npm ERR! path C:\Users\anton\Desktop\Projects\TextAdventures\package.json ( init without -y doesn't work either): > npm init -y It used to work fine before and yet even though I haven't updated anything etc. In that case, nothing you can do until the package maintainers for LWC plugins updates their manifest to use new projects (which also typically means altering code, so be patient).I've not been using node for a little bit ~1-2 months. You may get some "npm WARN deprecated" messages, too. You may need to adjust the above installation command to fix this problem. This means you've installed the wrong version of eslint. You must install peer dependencies yourself. If you see this, you need to select a new version of plugins until you run out of deprecated messages (if possible), and unmet peer dependencies.įor example: npm WARN requires a peer of || ^4.0.0 || ^5.0.0 || ^6.0.0 but none is installed. Instead, run: npm install typescript -save-devĪt some point, you may get warnings about things being deprecated or other unmet peer dependencies. The default force:package:create and subsequent installation of the Salesforce Extension Pack won't fully fix a myriad of small problems you'll encounter until you run npm install.įinally, the install steps seem to be incorrect some of the referenced packages are deprecated. What you do want to do is run npm install, as this actually installs a number of dependencies, and almost everything else you need to get things up and running. It's worth noting that apparently, babel-eslint is already present when you force:project:create (maybe it was accidentally removed in a previous release?) If you insist on doing npm init anyways, just press Enter/Return to accept all defaults (unless you want to provide any extra details). In other words, it adds a little extra info that you don't need (because you're not making an npm package, you're using it to save your dependencies and scripts). I just did a test to verify, and the diff between what force:project:create and all npm init does is: -39,5 +39,8 [ You don't need npm init if you use force:project:create.
0 kommentar(er)
