These are chat archives for reactioncommerce/reaction

29th
Jul 2016
Brent Hoover
@zenweasel
Jul 29 2016 02:30
Not sure why that links is broken, should work
madhavKushwaha
@madhavKushwaha
Jul 29 2016 03:50
Reaction CLI: 0.3.10
v4.4.7
2.15.8
Windows 10
As per your question...
madhavKushwaha
@madhavKushwaha
Jul 29 2016 04:05
Thank You
Help me Plz
Brent Hoover
@zenweasel
Jul 29 2016 04:08
I’m sorry, everyone was helping you has probably gone to bed as it’s past midnight on the East Coast
what was the issue you were having?
madhavKushwaha
@madhavKushwaha
Jul 29 2016 04:10
I got

operable program or batch file.
[[[[[ C:\REACTION\reaction ]]]]]

=> Started proxy.
=> Meteor 1.4 is available. Update this project with 'meteor update'.
=> Started MongoDB.
W20160729-09:30:40.960(5.5)? (STDERR)
W20160729-09:30:41.661(5.5)? (STDERR) C:\REACTION\reaction\node_modules\fibers\fibers.js:16
W20160729-09:30:41.662(5.5)? (STDERR) throw new Error(''+ modPath+ '.node is missing. Try reinstalling node-fibe W20160729-09:30:41.662(5.5)? (STDERR) ^ W20160729-09:30:41.663(5.5)? (STDERR) Error:C:\REACTION\reaction\node_modules\fibers\bin\win32-ia32-v8-3.14\fibers.nodeis missing. Try reinstallingnode-fibers`?
W20160729-09:30:41.663(5.5)? (STDERR) at Object.<anonymous> (C:\REACTION\reaction\node_modules\fibers\fibers.js:16:8)
W20160729-09:30:41.663(5.5)? (STDERR) at Module._compile (module.js:456:26)
W20160729-09:30:41.664(5.5)? (STDERR) at Object.Module._extensions..js (module.js:474:10)
W20160729-09:30:41.665(5.5)? (STDERR) at Module.load (module.js:356:32)
W20160729-09:30:41.665(5.5)? (STDERR) at Function.Module._load (module.js:312:12)
W20160729-09:30:41.666(5.5)? (STDERR) at Module.require (module.js:364:17)
W20160729-09:30:41.667(5.5)? (STDERR) at require (module.js:380:17)
W20160729-09:30:41.667(5.5)? (STDERR) at Object.<anonymous> (C:\REACTION\reaction.meteor\local\build\programs\server\boot.js:1:75)
W20160729-09:30:41.668(5.5)? (STDERR) at Module._compile (module.js:456:26)
W20160729-09:30:41.669(5.5)? (STDERR) at Object.Module._extensions..js (module.js:474:10)
=> Exited with code: 8

C:\Users\DCPLMADHAV>reaction -v
Reaction CLI: 0.3.10

C:\Users\DCPLMADHAV>node -v
v4.4.7

C:\Users\DCPLMADHAV>npm -v
2.15.8

Jeremy Shimko
@jshimko
Jul 29 2016 04:11
@madhavKushwaha have you installed the Microsoft Build Tools?
madhavKushwaha
@madhavKushwaha
Jul 29 2016 04:11
how to know about that??
After that, Problem will be solve??
Jeremy Shimko
@jshimko
Jul 29 2016 04:13
Some NPM packages require a platform specific binary to be compiled (like Fibers) and those are the build tools to do it on Windows.
madhavKushwaha
@madhavKushwaha
Jul 29 2016 04:13
ok
Thank you sir
Now I trying according to u
Jeremy Shimko
@jshimko
Jul 29 2016 04:15
It’s after midnight here, so I’m stepping away for the night, but I’ll check back in tomorrow. Good luck.
madhavKushwaha
@madhavKushwaha
Jul 29 2016 04:15
ok Sir Thanks...
madhavKushwaha
@madhavKushwaha
Jul 29 2016 04:52

$ reaction init

Cloning the master branch of Reaction from Github...
Cloning into 'reaction'...

Installing NPM packages...
npm WARN deprecated tough-cookie@2.2.2: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130

dtrace-provider@0.6.0 install C:\Users\DCPLMADHAV\AppData\Local\reaction\node_modules\dtrace-provider
node scripts/install.js

fibers@1.0.13 install C:\Users\DCPLMADHAV\AppData\Local\reaction\node_modules\fibers
node build.js || nodejs build.js

win32-ia32-v8-4.5 exists; testing
Binary is fine; exiting

reaction@0.14.1 postinstall C:\Users\DCPLMADHAV\AppData\Local\reaction
.reaction/scripts/postinstall.sh

'.reaction' is not recognized as an internal or external command,
operable program or batch file.

npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Users\DCPLMADHAV\AppData\Local\.meteor\packages\meteor-tool\1.4.0\mt-os.windows.x86_32\dev_bundle\bin\node.exe" "C:\Users\DCPLMADHAV\AppData\Local\.meteor\packages\meteor-tool\1.4.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.4.7
npm ERR! npm v3.10.5
npm ERR! code ELIFECYCLE
npm ERR! reaction@0.14.1 postinstall: .reaction/scripts/postinstall.sh
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the reaction@0.14.1 postinstall script '.reaction/scripts/postinstall.sh'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the reaction package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! .reaction/scripts/postinstall.sh
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs reaction
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls reaction
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\DCPLMADHAV\AppData\Local\reaction\npm-debug.log

Reaction successfully installed!

To start your Reaction instance, just run:

cd reaction
reaction

?─────────────────────────────────────────?
│ │
│ Update available 0.3.10 → 0.3.12 │
│ Run npm i -g reaction-cli to update │
│ │
?─────────────────────────────────────────?

madhavKushwaha
@madhavKushwaha
Jul 29 2016 04:58
Hello Sir,
Anyone is there???
Jeremy Shimko
@jshimko
Jul 29 2016 05:00
Known issue. Windows + bash === :worried:
I’ll fix it tomorrow.
madhavKushwaha
@madhavKushwaha
Jul 29 2016 05:06
Means????
Windows + bash???
Jeremy Shimko
@jshimko
Jul 29 2016 05:08
It means Windows doesn’t run bash scripts without extra effort. I’m going to rewrite that bash script as a Node script instead of asking every Windows user to deal with it themselves.
Getting things working on Windows is already hard enough.
madhavKushwaha
@madhavKushwaha
Jul 29 2016 05:10
How it will be solved
??
Jeremy Shimko
@jshimko
Jul 29 2016 05:10
I’m going to rewrite that bash script as a Node script
madhavKushwaha
@madhavKushwaha
Jul 29 2016 05:10
ok
Jeremy Shimko
@jshimko
Jul 29 2016 05:11
(tomorrow)
madhavKushwaha
@madhavKushwaha
Jul 29 2016 05:11
Thank you sir, Plz tell me after complete
Jeremy Shimko
@jshimko
Jul 29 2016 05:11
Will do
hrath2015
@hrath2015
Jul 29 2016 05:13
@madhavKushwaha in meantime do one thing. Go to Package.json and delete the line fibers from dependency
Jeremy Shimko
@jshimko
Jul 29 2016 05:15
Pretty sure the fibers issue was because of missing build tools
madhavKushwaha
@madhavKushwaha
Jul 29 2016 05:22
Confuse..
madhavKushwaha
@madhavKushwaha
Jul 29 2016 05:27
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.14
I got when ...... npm i -g reaction-cli
This error??? can effect
??
Brent Hoover
@zenweasel
Jul 29 2016 05:30
@madhavKushwaha Hey, it looks like we are still having some issues with Windows. @jshimko is going to work on it tomorrow and hopefully have a fix so that installation is easier on Windows. But he can’t continue troubleshooting with you because it’s the middle of the night.
Just hold tight and we will get you working soon
but tomorrow US time
madhavKushwaha
@madhavKushwaha
Jul 29 2016 05:34
ok
Thank You Sir
Gn Sir
hrath2015
@hrath2015
Jul 29 2016 05:43
@madhavKushwaha if you have gitbash installed then u can use the shell to run the script. See below
blob
This message was deleted
This message was deleted
sorry got loaded twice
This message was deleted
madhavKushwaha
@madhavKushwaha
Jul 29 2016 09:39
I did that
but problem not solved
Also when I do in linux I got:

[root@s45-40-134-145 reaction]# reaction

Using settings file at settings/dev.settings.json

Setting up plugin imports...

[[[[[ ~/reaction ]]]]]

=> Started proxy.
FATAL ERROR: Malloced operator new Allocation failed - process out of memory
/tmp/shelljs_0899a904ac45d78cea88:4
fs.writeFileSync("/tmp/shelljs_4c40b782ffcfa2ccf272", err ? err.code.toString() : '0');
^

TypeError: Cannot read property 'toString' of null
at /tmp/shelljs_0899a904ac45d78cea88:4:71
at ChildProcess.exithandler (child_process.js:209:5)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at maybeClose (internal/child_process.js:852:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
exec: internal error

swamykumarv
@swamykumarv
Jul 29 2016 12:18
Hi
Brent Hoover
@zenweasel
Jul 29 2016 12:18
Hello
swamykumarv
@swamykumarv
Jul 29 2016 12:19
I am trying to install but facing this issue
W20160729-17:49:11.556(5.5)? (STDERR)
W20160729-17:49:11.928(5.5)? (STDERR) C:\Users\kuvishnu\Desktop\xamp\htdocs\reac
tion\node_modules\fibers\fibers.js:16
W20160729-17:49:11.928(5.5)? (STDERR) throw new Error(''+ modPath+ '.node is
missing. Try reinstalling node-fibe W20160729-17:49:11.938(5.5)? (STDERR) ^ W20160729-17:49:11.938(5.5)? (STDERR) Error:C:\Users\kuvishnu\Desktop\xamp\htd
ocs\reaction\node_modules\fibers\bin\win32-ia32-v8-3.14\fibers.nodeis missing. Try reinstallingnode-fibers`?
W20160729-17:49:11.938(5.5)? (STDERR) at Object.<anonymous> (C:\Users\kuvish
nu\Desktop\xamp\htdocs\reaction\node_modules\fibers\fibers.js:16:8)
W20160729-17:49:11.938(5.5)? (STDERR) at Module._compile (module.js:456:26)
W20160729-17:49:11.938(5.5)? (STDERR) at Object.Module._extensions..js (modu
le.js:474:10)
W20160729-17:49:11.938(5.5)? (STDERR) at Module.load (module.js:356:32)
W20160729-17:49:11.938(5.5)? (STDERR) at Function.Module._load (module.js:31
2:12)
W20160729-17:49:11.938(5.5)? (STDERR) at Module.require (module.js:364:17)
W20160729-17:49:11.938(5.5)? (STDERR) at require (module.js:380:17)
W20160729-17:49:11.938(5.5)? (STDERR) at Object.<anonymous> (C:\Users\kuvish
nu\Desktop\xamp\htdocs\reaction.meteor\local\build\programs\server\boot.js:1:75
)
W20160729-17:49:11.938(5.5)? (STDERR) at Module._compile (module.js:456:26)
W20160729-17:49:11.938(5.5)? (STDERR) at Object.Module._extensions..js (modu
le.js:474:10)
Brent Hoover
@zenweasel
Jul 29 2016 12:22
Did you install the extra Windows requirements?
swamykumarv
@swamykumarv
Jul 29 2016 12:23
Yes, these 4 right
Node.js >=4.x.x (with NPM)
Win32 OpenSSL (windows installer) (See npm-node-aes-gcm/README.md)
Microsoft Build Tools 2015
Git + msysGit (git-for-windows/git)
ImageMagick
Brent Hoover
@zenweasel
Jul 29 2016 12:25
You are using master?
swamykumarv
@swamykumarv
Jul 29 2016 12:26
yes
I did react init
then I think it's pulled from master
Brent Hoover
@zenweasel
Jul 29 2016 12:27
Yeah honestly I don’t know what that issue is but people on Windows are running into it with the migration to Meteor 1.4. I know @jshimko was working on it but I don’t know what the solution is
I think we should have a fix for it shortly. It’s still just morning in the US
swamykumarv
@swamykumarv
Jul 29 2016 12:29
Oh! Yes, sorry for disturbing you early morning
Brent Hoover
@zenweasel
Jul 29 2016 12:30
No, it’s daytime here, but the guy who is working on it is in the US
:)
swamykumarv
@swamykumarv
Jul 29 2016 12:31
Okay
'.reaction' is not recognized as an internal or external command,
operable program or batch file.
also I am getting above message
when I do reaction start
Brent Hoover
@zenweasel
Jul 29 2016 12:35
Yeah, you don’t want to put the period before it when running it
Jeremy Shimko
@jshimko
Jul 29 2016 12:35
Yes, it’s for the same reason I said above. We’ll let you know when a new release is out today. Sorry for the inconvenience.
Windows is the only platform that doesn’t natively run bash scripts and we use them.
Brent Hoover
@zenweasel
Jul 29 2016 12:35
So just chill ;)
we’ll have a fix soon and we’ll post it here or you can watch the reaction-cli repo
it’s not you, it’s us
Jeremy Shimko
@jshimko
Jul 29 2016 12:39

In the meantime, you should probably be able to run these commands from the Reaction directory to get the app started.

meteor npm install
meteor

If that doesn’t work, then reaction-cli isn’t your issue.

swamykumarv
@swamykumarv
Jul 29 2016 12:39
Oh! Okay, Thanks Jeremy & Brent, will wait for build
meteor run also throwing same issue
so, it's reaction-cli issues and need to wait for update?
Jeremy Shimko
@jshimko
Jul 29 2016 12:44
not if meteor the same thing
yes, the cli needs an update, but it doesn’t sound like that’s your problem
Have you installed the Microsoft Build Tools?
Brent Hoover
@zenweasel
Jul 29 2016 12:45
lol, I asked him that already
swamykumarv
@swamykumarv
Jul 29 2016 12:46
yes
Brent Hoover
@zenweasel
Jul 29 2016 12:46
he did
Jeremy Shimko
@jshimko
Jul 29 2016 12:46
sorry, scanned the conversation and didn’t see it
Brent Hoover
@zenweasel
Jul 29 2016 12:46
@swamykumarv
Yes, these 4 right
Node.js >=4.x.x (with NPM)
Win32 OpenSSL (windows installer) (See npm-node-aes-gcm/README.md)
Microsoft Build Tools 2015
Git + msysGit (git-for-windows/git)
ImageMagick
Jeremy Shimko
@jshimko
Jul 29 2016 12:46
can you run reaction -v
swamykumarv
@swamykumarv
Jul 29 2016 12:46
after microsoft build tool install, do I need to restart my machine?
Jeremy Shimko
@jshimko
Jul 29 2016 12:46
not sure, but I don’t think so
Brent Hoover
@zenweasel
Jul 29 2016 12:47
I don’t know of a good way to test whether the MSBuild tool are working
swamykumarv
@swamykumarv
Jul 29 2016 12:47
issue saying try to install node-fibers
Brent Hoover
@zenweasel
Jul 29 2016 12:47
Yeah, it needs the build tools to compile requirements which have a binary component
and fibers is one of those
this is all new in 1.4
swamykumarv
@swamykumarv
Jul 29 2016 12:50
reaction -v
Node: 4.4.5
NPM: 2.15.5
Reaction: 0.14.1
Reaction CLI: 0.3.12
Jeremy Shimko
@jshimko
Jul 29 2016 12:51
thank you.
swamykumarv
@swamykumarv
Jul 29 2016 12:54
I will try by restarting my mechine, will get back in a3 min
Brent Hoover
@zenweasel
Jul 29 2016 12:54
Ok, we’re debating what the issue might be
Can you try removing fibers from the package.json?
hrath2015
@hrath2015
Jul 29 2016 12:57
guess there are many things changed in 1.4. One of them is npm-bcrypt package which also need binary. For me It is down completely for 1.4. As the machine I have can't install MS build stuff. Will get another machine tomorrow and see what is the cause
Jeremy Shimko
@jshimko
Jul 29 2016 12:58
Yeah, build tools aren’t optional on any platform.
It’s a separate install on OS X and Linux too
Brent Hoover
@zenweasel
Jul 29 2016 12:58
I can speak from experience that it’s 100% harder on Windows
hrath2015
@hrath2015
Jul 29 2016 12:58
So far I was managing without MS build stuff. Now I think no more. Will be switching over to linux ubuntu
Brent Hoover
@zenweasel
Jul 29 2016 12:58
installing build tools I mean
Jeremy Shimko
@jshimko
Jul 29 2016 12:59
yes please
Brent Hoover
@zenweasel
Jul 29 2016 12:59
No quick command line
@hrath2015 so is it Reaction that you can’t use w/o the build tools, or just Meteor in general?
hrath2015
@hrath2015
Jul 29 2016 13:02
and there is no option to go back. did not work --release METEOR@1.3.5.1
it is meteor
Brent Hoover
@zenweasel
Jul 29 2016 13:02
because none of our dependencies have a binary component
Jeremy Shimko
@jshimko
Jul 29 2016 13:02
yeah, a few do
Brent Hoover
@zenweasel
Jul 29 2016 13:02
when I saw that in the release notes I had this feeling this was going ot happen
Reaction dependencies?
swamykumarv
@swamykumarv
Jul 29 2016 13:03
how to find meteor version?
I think I am not using meteor 1.4
Jeremy Shimko
@jshimko
Jul 29 2016 13:03
you are
Reaction 0.14.1 is
Brent Hoover
@zenweasel
Jul 29 2016 13:03
Reaction specifies which version of Meteor to use
swamykumarv
@swamykumarv
Jul 29 2016 13:03
okay
Brent Hoover
@zenweasel
Jul 29 2016 13:04
@swamykumarv What happens if you type msbuild at the command line?
Jeremy Shimko
@jshimko
Jul 29 2016 13:04
you can always confirm by looking at .meteor/release inside any Meteor project
hrath2015
@hrath2015
Jul 29 2016 13:04
fibers and oauth-encryptio were manageable. bcrypt and others no.
swamykumarv
@swamykumarv
Jul 29 2016 13:04
but still showing when update meteor 1.4 available
hrath2015
@hrath2015
Jul 29 2016 13:04
@swamykumarv just try meteor in your project dir and see what happens
swamykumarv
@swamykumarv
Jul 29 2016 13:05
showing same error
Brent Hoover
@zenweasel
Jul 29 2016 13:05
he tried that already, same error
swamykumarv
@swamykumarv
Jul 29 2016 13:05
'msbuild' is not recognized as an internal or external command,
operable program or batch file.
msbuild not recognized
is this issue Brent?
hrath2015
@hrath2015
Jul 29 2016 13:06
meteor --version what it shows
Brent Hoover
@zenweasel
Jul 29 2016 13:06
it’s been a while since I’ve used Windows, but I think that should work if the MSBuild tools are properly installed
what version does meteor —version show?
swamykumarv
@swamykumarv
Jul 29 2016 13:07
in meteor versions I saw that it's "meteor@1.1.16"
Brent Hoover
@zenweasel
Jul 29 2016 13:07
wait what?
Jeremy Shimko
@jshimko
Jul 29 2016 13:07
??
hrath2015
@hrath2015
Jul 29 2016 13:07
type is on command prompt
please type on command prompt
meteor --version
u should get Meteor 1.4
Jeremy Shimko
@jshimko
Jul 29 2016 13:08
.meteor/release
swamykumarv
@swamykumarv
Jul 29 2016 13:08
Meteor 1.3.5.1
it's
hrath2015
@hrath2015
Jul 29 2016 13:08
u r on master
branch of RC
Jeremy Shimko
@jshimko
Jul 29 2016 13:09
oh wait, yep
reaction init -b development
yeah, master is still on 1.3.5.1
Jeremy Shimko
@jshimko
Jul 29 2016 13:09
That would be 1.4
hrath2015
@hrath2015
Jul 29 2016 13:09
please do that in fresh directory
Brent Hoover
@zenweasel
Jul 29 2016 13:09
so then I really don’t know what the issue is
hrath2015
@hrath2015
Jul 29 2016 13:09
what @jshimko is suggesting
Jeremy Shimko
@jshimko
Jul 29 2016 13:10
or just git checkout development in the existing one
swamykumarv
@swamykumarv
Jul 29 2016 13:10
okay
Jeremy Shimko
@jshimko
Jul 29 2016 13:10
but start a fresh one just to be safe
hrath2015
@hrath2015
Jul 29 2016 13:10
sometimes on windows u should be lil extra careful
Jeremy Shimko
@jshimko
Jul 29 2016 13:10
sometimes?
;)
hrath2015
@hrath2015
Jul 29 2016 13:11
:laughing:
Brent Hoover
@zenweasel
Jul 29 2016 13:11
Windows guys, amirite?
swamykumarv
@swamykumarv
Jul 29 2016 13:12
now it's Meteor 1.4
Jeremy Shimko
@jshimko
Jul 29 2016 13:12
I love how even Microsoft has given up on trying to run bash on Windows
https://msdn.microsoft.com/en-us/commandline/wsl/about
Brent Hoover
@zenweasel
Jul 29 2016 13:13
can’t you run Ubuntu bash in Win10?
swamykumarv
@swamykumarv
Jul 29 2016 13:13
now I am getting below issue

While checking for npm-node-aes-gcm@0.1.7_4:
error: No compatible binary build found for this package. Contact the
package author and ask them to publish it for your platform.

Your application has errors. Waiting for file change.

hrath2015
@hrath2015
Jul 29 2016 13:13
it means u don't have build tool installed
Jeremy Shimko
@jshimko
Jul 29 2016 13:13
yep, that’s build tools not working
hrath2015
@hrath2015
Jul 29 2016 13:14
or working partially
Brent Hoover
@zenweasel
Jul 29 2016 13:14
I am pretty sure that running msbuild needs to work from the command line
swamykumarv
@swamykumarv
Jul 29 2016 13:14
I have installed it
Brent Hoover
@zenweasel
Jul 29 2016 13:14
because that’s what Meteor is going to be doing
swamykumarv
@swamykumarv
Jul 29 2016 13:14
Okay, then I need to change environment parameter may be
Brent Hoover
@zenweasel
Jul 29 2016 13:15
I am just using that as the canary in the coalmine to test whether it’s installed correctly or not
possibly something with pathing, etc.
hrath2015
@hrath2015
Jul 29 2016 13:15
u do 1 thing in meantime go packages file in .meteor dir
hrath2015
@hrath2015
Jul 29 2016 13:15
comment this line like #oauth-encryptio
Jeremy Shimko
@jshimko
Jul 29 2016 13:15
Apparently you might still need a dependency from 2008. Right on Windows, right on.
hrath2015
@hrath2015
Jul 29 2016 13:16
once done restart. U should not get this error.
Jeremy Shimko
@jshimko
Jul 29 2016 13:17
Really? You have to restart after installing build tools before using them?
Brent Hoover
@zenweasel
Jul 29 2016 13:18
I think he meant restart reaction
hrath2015
@hrath2015
Jul 29 2016 13:18
sorry I mean meteor
Jeremy Shimko
@jshimko
Jul 29 2016 13:18
ah
swamykumarv
@swamykumarv
Jul 29 2016 13:18
I think I don't have Visual Studio 2008
Brent Hoover
@zenweasel
Jul 29 2016 13:18
although a thorough rebooting never hurt anybody
hrath2015
@hrath2015
Jul 29 2016 13:18
it is not that bad @jshimko
Brent Hoover
@zenweasel
Jul 29 2016 13:19
yeah, y’all are making me feel a little sorry for windows right now
it’s that crazy versioning they use where 2008 is the current version
swamykumarv
@swamykumarv
Jul 29 2016 13:20
ha haa.. no problem
hrath2015
@hrath2015
Jul 29 2016 13:20
@swamykumarv please comment the line and see if that is the only issue
There are a bunch of versions. I don’t know if the latest works. I never expect that from them though.
Brent Hoover
@zenweasel
Jul 29 2016 13:21
usually you need to use the version behind the latest to build open source stuff
swamykumarv
@swamykumarv
Jul 29 2016 13:21
@hrath, what should I comment?
Jeremy Shimko
@jshimko
Jul 29 2016 13:21
swamykumarv
@swamykumarv
Jul 29 2016 13:22
after installing visual studio you think I need install again OpenGSL?
Brent Hoover
@zenweasel
Jul 29 2016 13:22
I think too many years of reading MSDN articles prevents me from ever reading one again
hrath2015
@hrath2015
Jul 29 2016 13:22
comment this line like #oauth-encryptio in .meteor dir and packages file
OpenSSL i guess
swamykumarv
@swamykumarv
Jul 29 2016 13:22
ss
If they say install VS2008 that’s what I would do
hrath2015
@hrath2015
Jul 29 2016 13:25
@swamykumarv what's happening?
swamykumarv
@swamykumarv
Jul 29 2016 13:26
I did removed it and trying
common.... now it's having an other issue :(
hrath2015
@hrath2015
Jul 29 2016 13:27
like
swamykumarv
@swamykumarv
Jul 29 2016 13:28

While downloading npm-bcrypt@0.8.7...:
error: Command failed:
C:\Users\kuvishnu\AppData\Local.meteor\packages\meteor-tool\1.4.0\mt-os.wind
s.x86_32\dev_bundle\bin\npm.cmd
rebuild --no-bin-links --update-binary
gyp ERR! build error
gyp ERR! stack Error: C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit
(C:\Users\kuvishnu\AppData\Local.meteor\packages\meteor-tool\1.4.0\mt-os.win
ws.x86_32\dev_bundle\lib\node_modules\node-gyp\lib\build.js:276:23)
gyp ERR! stack at emitTwo (events.js:87:13)
gyp ERR! stack at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit
(internal/child_process.js:200:12)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command
"C:\Users\kuvishnu\AppData\Local\.meteor\packages\meteor-tool\1.4.0\
-os.windows.x86_32\dev_bundle\bin\node.exe"
"C:\Users\kuvishnu\AppData\Local\.meteor\packages\meteor-tool\1.4.0\
-os.windows.x86_32\dev_bundle\lib\node_modules\node-gyp\bin\node-gyp.js"

"rebuild"
gyp ERR! cwd
C:\Users\kuvishnu\AppData\Local\Temp\mt-fup4w4\npm\node_modules.temp-y51ev6\
de_modules\bcrypt
gyp ERR! node -v v4.4.7
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok

npm ERR! Windows_NT 6.1.7601
npm ERR! argv
"C:\Users\kuvishnu\AppData\Local\.meteor\packages\meteor-tool\1.4.0\
-os.windows.x86_32\dev_bundle\bin\node.exe"
"C:\Users\kuvishnu\AppData\Local\.meteor\packages\meteor-tool\1.4.0\
-os.windows.x86_32\dev_bundle\lib\node_modules\npm\bin\npm-cli.js"
"rebuild" "--no-bin-links" "--update-binary"
npm ERR! node v4.4.7
npm ERR! npm v3.10.5
npm ERR! code ELIFECYCLE
npm ERR! bcrypt@0.8.7 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bcrypt@0.8.7 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm
installed.
npm ERR! If you do, this is most likely a problem with the bcrypt
package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get information on how to open an issue for this
project with:
npm ERR! npm bugs bcrypt
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls bcrypt
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!
C:\Users\kuvishnu\AppData\Local\Temp\mt-fup4w4\npm\node_modules.temp-y51ev6\
m-debug.log
gyp ERR! build error
gyp ERR! stack Error: C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit
(C:\Users\kuvishnu\AppData\Local.meteor\packages\meteor-tool\1.4.0\mt-os.win
ws.x86_32\dev_bundle\lib\node_modules\node-gyp\lib\build.js:276:23)
gyp ERR! stack at emitTwo (events.js:87:13)
gyp ERR! stack at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit
(internal/child_process.js:200:12)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command
"C:\Users\kuvishnu\AppData\Local\.meteor\packages\meteor-tool\1.4.0\
-os.windows.x86_32\dev_bundle\bin\node.exe"
"C:\Users\kuvishnu\AppData\Local\.meteor\packages\meteor-tool\1.4.0\
-os.windows.x86_32\dev_bundle\lib\node_modules\node-gyp\bin\node-gyp.js"

"rebuild"
gyp ERR! cwd
C:\Users\kuvishnu\AppData\Local\Temp\mt-fup4w4\npm\node_modules.temp-y51ev6\
de_modules\bcrypt
gyp ERR! node -v v4.4.7
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok

npm ERR! Windows_NT 6.1.7601
npm ERR! argv
"C:\Users\kuvishnu\AppData\Local\.meteor\packages\meteor-tool\1.4.0\
-os.windows.x86_32\dev_bundle\bin\node.exe"
"C:\Users\kuvishnu\AppData\Local\.meteor\packages\meteor-tool\1.4.0\
-os.windows.x86_32\dev_bundle\lib\node_modules\npm\bin\npm-cli.js"
"rebuild" "--no-bin-links" "--update-binary"

hrath2015
@hrath2015
Jul 29 2016 13:28
this is what I suspected.
Please follow all the steps for windows (2008 etc..) then try
swamykumarv
@swamykumarv
Jul 29 2016 13:29
Okay, I will try freshly again
hrath2015
@hrath2015
Jul 29 2016 13:30
Once u are done with all installation, please re start your machine. Good luck
swamykumarv
@swamykumarv
Jul 29 2016 13:30
Okay
hrath2015
@hrath2015
Jul 29 2016 13:30
then fire up reaction.
tc bye
Brent Hoover
@zenweasel
Jul 29 2016 13:33
well, that went well
Aaron Judd
@aaronjudd
Jul 29 2016 15:31
@3Maestros re: question about if anyone has built a native -> I”m sure there’s a few, but the only one I’ve seen in the wild was someone published an Android native Reaction a few months ago. unfortunately, I don’t remember who/or the name they gave it but I saw it ;-)
3Maestros
@3Maestros
Jul 29 2016 16:12
@aaronjudd Are you referring to "Reaction Commerce Demo" app? I found this on Android couple od weeks ago , it comes back with error "demo.reactioncommerce.com" could not be loaded net:ERR_EMPTY_RESPONSE
Aaron Judd
@aaronjudd
Jul 29 2016 16:16
Yes, I think that’s the one.. I really don’t know anything about it, but we tried it when we first saw it and it was working, I’m going to guess that was around v0.8 or so. (obviously not maintained, I guess)
3Maestros
@3Maestros
Jul 29 2016 16:17
yes looks like it ...
Aaron Judd
@aaronjudd
Jul 29 2016 16:18
one of our team is going to work on getting compiles going in that issue we created, but he’s out next week, so probably a bit more time, but if you want to log any roadblocks you’re getting in that issue, we’ll work through them
3Maestros
@3Maestros
Jul 29 2016 16:20
@aaronjudd yes thanks, I plan to try building for mobile this week and log any issue I encounter.
Aaron Judd
@aaronjudd
Jul 29 2016 16:24
:thumbsup: