Closed jjdp closed 9 years ago
It's also confirmed on OSX. Something has changed in the last Atom's update. Weird.
Thanks for the warning.
open and close developer tools once you launch meteor, the logs will start to show up.
It now gives me the tasklist error. Tried the advanced method from the readme. But it also gives me this.
What's wrong with this bat? @echo off SETLOCAL SET PATH=C:\Windows\system32;C:\Users\Jan\AppData\Local.meteor\;C:\Users\Jan\AppData\Local\atom\bin SET METEOR_INSTALLATION=%~dp0% "%~dp0\packages\meteor-tool\1.1.8\mt-os.windows.x86_32\meteor.bat" %* ENDLOCAL EXIT /b %ERRORLEVEL% rem %~dp0\packages\meteor-tool\1.1.8\mt-os.windows.x86_32\meteor.bat
Please see if mongo process was killed properly, solved the same problem for me – it was due to wrongly seth paths and application crashing before killing it.
About those paths – I found that if I already have meteor directory added to system PATH
I coud just set "Meteor Path" in extension settings to:
meteor.bat
and it just worked.
(Please note that you do not need to create or modify any file on your filesystem in this solution).
And if this doesn't work then probably there is no meteor directory in system path variable – you can fix it by adding it permanently by typing in command line:
SET PATH=%PATH%;C:\Users\username\AppData\Local\.meteor\
(You can remove it later if you want of course, but it's really good thing to have; and if you want to use several different versions of meteor, I would suggest just creating many .bat files pointing to them in the meteor directory that was added to path, and just edit their contents to create/overwrite default meteor.bat file to point to different installs inside, and later just delete default meteor.bat, to now use unknown installation in case of something crashing... but these are just my loose thoughts).
EDIT: short explanation – it works, because it runs from your app directory – if you will give full path to meteor.bat, it treats meteor.bat's directory as local; not sure why just putting "meteor" work though;
Anyway, it would be maybe good idea to allow to run local file with different name than meteor – then we could create .bat file with contents as follows:
@echo off
SETLOCAL
SET PATH=%PATH%;C:\Users\TTT\AppData\Local\.meteor\
meteor
ENDLOCAL
(If somebody don't want set path permanently).
@sdinesh86 Thanks! That solve the problem
Fixed in 0.27.0.
excellent
This may be windows' fault. I am on windows 10 64-bit. When I launch my app using atom, it doesn't show anything except for the warning icon continuing to blink. Although it can run when just using the command prompt.