Npm install errors

[steveknoblock]

I am trying to install TME in a new project as the first thing I add, but I get this result:

PS C:\Users\Steve\Dropbox\Projects\QuickSlow\QuickSlow> npm install --save tiny-markdown-editor
npm WARN rollback Rolling back core-js@3.38.1 failed (this is probably harmless): EBUSY: resource busy or locked, rmdir 'C:\Users\Steve\Dropbox\Projects\QuickSlow\QuickSlow\node_modules'
npm ERR! code ENOENT
npm ERR! syscall rename
npm ERR! path C:\Users\Steve\Dropbox\Projects\QuickSlow\QuickSlow\node_modules\tiny-markdown-editor
npm ERR! dest C:\Users\Steve\Dropbox\Projects\QuickSlow\QuickSlow\node_modules\.tiny-markdown-editor.DELETE
npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, rename 'C:\Users\Steve\Dropbox\Projects\QuickSlow\QuickSlow\node_modules\tiny-markdown-editor' -> 'C:\Users\Steve\Dropbox\Projects\QuickSlow\QuickSlow\node_modules\.tiny-markdown-editor.DELETE'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent 

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Steve\AppData\Roaming\npm-cache\_logs\2024-09-25T18_42_26_634Z-debug.log

[steveknoblock]

I just ran it without the recommended save option. It installed.

PS C:\Users\Steve\Dropbox\Projects\QuickSlow\QuickSlow> npm install tiny-markdown-editor

core-js@3.38.1 postinstall C:\Users\Steve\Dropbox\Projects\QuickSlow\QuickSlow\node_modules\core-js node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting core-js:

https://opencollective.com/core-js https://patreon.com/zloirock https://boosty.to/zloirock bitcoin: bc1qlea7544qtsmj2rayg0lthvza9fau63ux0fstcz

I highly recommend reading this: https://github.com/zloirock/core-js/blob/master/docs/2023-02-14-so-whats-next.md

npm notice created a lockfile as package-lock.json. You should commit this file.

• tiny-markdown-editor@0.1.24 added 2 packages from 2 contributors and audited 2 packages in 7.459s

1 package is looking for funding run npm fund for details

found 0 vulnerabilities

[jefago]

Pretty sure that was a glitch in npm or some kind of npm caching issue (and/or that you installed this just while I was releasing a new version of the package!). All that the --save option does is add the installed package to your package.json, it shouldn't affect the installation process at all.