My surprise is I’ve worked with it before but this time I can’t.
I get this message:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\lingo57>cd meteor
C:\Users\lingo57\Meteor>cd meteor_try
C:\Users\lingo57\Meteor\Meteor_Try>meteor run
C:\Users\lingo57\AppData\Local\.meteor\packages\meteor-tool\1.6.0_1\mt-os.window
s.x86_32\dev_bundle\lib\node_modules\meteor-promise\promise_server.js:218
throw error;
^
Error: EPERM: operation not permitted, unlink 'C:\Users\lingo57\Meteor\Meteor_Tr
y\.meteor\local\dev_bundle'
at Object.fs.unlinkSync (fs.js:1061:18)
at exports.makeLink (C:\tools\cli\dev-bundle-links.js:20:8)
at exports.ReleaseFile.ensureDevBundleLink (C:\tools\project-context.js:1507
:7)
at exports.ReleaseFile._readFile (C:\tools\project-context.js:1441:10)
at new exports.ReleaseFile (C:\tools\project-context.js:1391:8)
at C:\tools\cli\main.js:923:22
C:\Users\lingo57\Meteor\Meteor_Try>
C:\Users\lingo57\Meteor\Meteor_Try>
That was an issue with npm 5.4, but it’s been fixed with npm 5.6. Meteor 1.6.1 uses npm 5.6. I’m wondering if you’ve installed node.js and npm separately from Meteor and used npm commands instead of meteor npm commands at some time.
Yes, the simplest fix for a local meteor install issue is to run meteor reset or delete your .meteor/local folder.
And yes this will delete your development db. Which is why you shouldn’t put data in the development db that has to stay there.
For development I recommend putting some fixtures (a basic set of data for development purposes) in your server startup files. Then you can safely wipe your db and it will be re-created and populated on the next run
i download examples -todos ,after meteor npm install , when i try meteor it download meteor-tools@1.6.0.1 . and it is extremely slowly and i wonder where is wrong