New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[1.3.4.3 + windows] Error: EPERM, symlink ... dev_bundle #7374
Comments
Same here, windows 8.1 Can't do anything.. Can't run any apps, update meteor, or even check what version I'm on - just get the same error you are. |
Same here, I am on windows10 It was working a few hours ago, and all of sudden it stopped working and giving this error. |
Same here on Windows 10. |
I got it for windows 7 |
any workarounds would help.. completely blocked..not able to do any thing. |
How can I downgrade the meteor-tool and stop the automatic update ? |
Same here I tried uninstalling, reinstalling but the bug is still here on windows 10. Whenever I try to create a new project with an old release meteor --release 1.3.2, I can't run with |
I found a way to downgrade to old version. there is a meteor.bat file @ C:\users\XYZ\AppData\Local .meteor @echo off |
I too facing same issue windows 7 |
In any way I hope such a problem will not happen again, and meteor will test its releases, a full framework who's front and back-end make code unusable without the framework. Without guaranties for the future, I'll definitively stop counting on the framework as a reliable solution... |
Same issue here... I will try Rahman's fix, in mean time this needs to be resolved. EDIT: On Windows 7. I personally did not have 1.3.4, so downgraded to 1.3.4_1 and it works now. |
same issue here. but there will no problem when i create app in c:/users/username. So i try to run as administrator and it works. |
Running the commandprompt as administrator works for me too. Before that i used Rahman's approach, in addition to which i made the meteor.bat file read-only, because it was overwritten each time i started meteor. |
I will unrecommend 1.3.4.3, which should prevent Can anyone provide a longer stack trace than what's already been provided? |
Is there a switch that i can use for a longer stack trace? I'd be glad to help out, but a clue would be welcome. |
Running the shell ( Alternatively, here's how you can grant a non-Administrator user the ability to create symbolic links (though it takes an Administrator to grant the privilege). I will note that One more question: Are your application directories also on the |
My applications are on another drive (not C:) Using |
@gjr-qm can you try creating an app on |
@benjamn your command produces the same error when i run it as a regular user. |
@benjamn These stack traces appear to be missing a slash in the path between
|
@abernix I think that's just from copy-pasting the |
Check! The \ is there in the stack traces |
My hunch is that the |
I think it is not the drive, because it doesn't matter on which drive i try to run or create the app, it always results in the error when i do it as a regular user. But when i run the command prompt/Powershell as administrator, then it simply works on all drives. |
This wouldn't work if .meteor/dev_bundle needed to be a true symbolic link, but fortunately we just need to record the target path in a way that allows us to read it later. Fixes #7374.
Great work, thanx @benjamn! |
This should be fixed if you |
in windows 10, I open dos command with administrator, then run meteor. It works. |
Doing |
An hour ago meteor-tool was automatically updated on my machine (Windows 10). After that my existing application resulted in an error when starting (meteor).
Creating a new project with 'meteor create test-app' doesn't work either. The error i get is:
...\AppData\Local.meteor\packages\meteor-tool\1.3.4_3\mt-os.windows.x86_32\dev_bundle\lib\node_modules\meteor-promise\promise_server.js:165
throw error;
^
Error: EPERM, symlink '...\AppData\Local.meteor\packages\meteor-tool\1.3.4_3\mt-os.windows.x86_32\dev_bundle'
I tried stepping back to version 1.3.4_1 (which worked), but then meteor-tool is automatically updated again to version 1.3.4_3.
Anyone else having this problem? And is there a workaround (previous version worked just fine)?
The text was updated successfully, but these errors were encountered: