-
Notifications
You must be signed in to change notification settings - Fork 82
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
Run error on Windows #138
Comments
Hmm does the nodes spawn command not work the same way on windows maybe? I may have to open up a VM and try it out.
|
Starting with meteor for me is also starting with node unfortunately. I didn't get any warnings about compatibility but you gave me at least a place to look into. Thanks! Not sure how much longer I'll keep my eyes open on this tonight but if I come across anything I'll let you know. For the record I'm using the latest meteor package 1.1.0.1 on Win8.1 |
Yeah keep me posted. Will keep a mental note to check this out on next cycle.
|
I am getting a similar error when I try to run Running windows 7 npm version 2.7.4, node v0.12.2
|
Same here |
Occur on windows 7 |
I've been hitting a few issues with some node modules and Windows lately. re-installing those modules specifically seems to help in a few of the cases. It may be worth a try to cd into the directory and run |
Trying... $ npm install
danjavia@DIEGOSHK /C/Users/danjavia/Desktop/Danjavia/shrmelink c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\node_modules\fibers\future.js:278 |
I'm getting the same error trying to run the PS F:\GitHub\Artisfy> iron C:\Users\Seeker\AppData\Roaming\npm\node_modules\iron-meteor\node_modules\fibers |
I get the same error on Windows 8.1. (error no. 193). Running Meteor 1.1.0.2. All latest Windows patches. |
I think this is because shell-source isn't windows compatible... In addition to the default source script provided, forward slashes are hardcoded as directory separators in index.js... |
Oops. That might be it. The purpose of that is to source the env.sh file. You can see the code in |
I like the idea of a PR to shell-source, but then again I'm bias as I just built my own PR for iron-meteor around shell-source features... Fixing the hard coded forward slash in their index.js and using my PR to expose a way to customize how env.sh is sourced could fix the problems for windows folks. |
Is this fixed ? I tried your fix @Mitzip but it didn't work for me. |
Same issue here. |
Is anybody fixed this issue? I met the same issue. |
I gave up a while ago and went with Flow Router. The idea of scaffolding On Sun, Jul 5, 2015 at 9:53 PM, Crystal2030 [email protected]
|
I also get this error, anybody knows if any fix is planned ? |
@ryanbuiltthat @Crystal2030 @Auryg @pavan4 @babin93 can you guys try to update to version 1.2.2 and see if that makes a difference? |
@chrisbutler installed right now and found this issue. In v1.2.2 it is same: |
hey everyone, hopefully this will fix the can you guys try this version and let me know if that fixes it?
|
Nice work chris. I wonder if it's better to just have the settings.json be the primary source of info, and it can read from environment variables for production environments. Those environment variables could be set in any number of ways. This would require putting the settings.json file through a template parser. It might be something like this: {
database_password: <%= process.env['DATABASE_PASSWORD'] %>
} |
thanks @spyhole. this fix is released in 1.3.1 |
@chrisbutler windows bugs(#198 #199) fixed with pull request #205 |
I'm trying to run my app using the
iron run
command or justiron
but I'm hitting an error...\npm\node_modules\iron-meteor\node_modules\fibers\future.js:278
Error: spawn Unknown system errno 193
I'm just going to go ahead and say it, I have no effin' clue what this means. :) The app seems to do ok if I
cd
into the app directory and just run meteor. Am I missing something here?The text was updated successfully, but these errors were encountered: