These are chat archives for reactioncommerce/reaction

6th
Jun 2017
juandanceswild
@juandanceswild
Jun 06 2017 00:51
Hi guys, I’m playing with Reaction for the first time locally and I’m having a hard time with the basics. When I create a new product and set all its properties, I publish it, but I still can’t add it to the cart (I get the message “Publish product before adding to cart.
“) even though it’s published
Also, in the store view, the details for the product - price, namely - aren’t updated
Brent Hoover
@zenweasel
Jun 06 2017 00:52
Make sure you have published all your variants and options (double-check that the eye icon is set to visible).
Spencer Norman
@spencern
Jun 06 2017 00:52
Check to make sure that 1. It’s Visible, 2. It has both a Title and an variant label, and 3. that it actually published
Spencer Norman
@spencern
Jun 06 2017 01:17
There’s a bug out there somewhere that I couldn’t quickly find the issue number for that is for this issue. Sometimes when you click publish if you haven’t set a title or a variant label, the UI will say “Published” but there will be a server error that causes the publish to fail.
Brent Hoover
@zenweasel
Jun 06 2017 01:18
pretty sure that was closed a while ago
Spencer Norman
@spencern
Jun 06 2017 01:21
Probably why I couldn’t find it
Brent Hoover
@zenweasel
Jun 06 2017 01:22
reactioncommerce/reaction#2225
ChanYu Chen
@j0214ack
Jun 06 2017 02:36
Hi guys, I am new to here. Tried to install reaction yesterday and accidentally updated meteor version to 1.5, and reaction started to report error. Is current version incompatible with meteor 1.5 ? I got this error msg:
Plugin 0 specified in "foreign" 
provided an invalid property of 
 "__wrapped__"  at Plugin.init
Brent Hoover
@zenweasel
Jun 06 2017 02:38
Yeah, the current version is not comptaible with Meteor 1.5. You might want to start with a fresh reaction init. We do have a branch that we are working on 1.5 compatabilty. reactioncommerce/reaction#2371
ChanYu Chen
@j0214ack
Jun 06 2017 02:41
Thanks a lot!! One more noob question: How do I downgrade meteor? And what's the highest version reaction is currently supporting?
Brent Hoover
@zenweasel
Jun 06 2017 02:41
unless you force an upgrade you will automatically get the correct version of Meteor
ChanYu Chen
@j0214ack
Jun 06 2017 02:42
Ah, I tried a fresh one but got the same error though, I thought it was the global meteor version issue
ChanYu Chen
@j0214ack
Jun 06 2017 02:43
yes, the fresh one shows the same release version
Brent Hoover
@zenweasel
Jun 06 2017 02:43
try doing meteor npm install within your new directory
at the root
Jeremy Shimko
@jshimko
Jun 06 2017 02:44
you can switch to another Meteor release with meteor update --release <version>
I believe that works in either direction
or just manually edit the file Brent linked
ChanYu Chen
@j0214ack
Jun 06 2017 02:46
no luck, after meteor npm install then reaction, i got this:
While processing files with ecmascript (for target web.browser):

 ${HOME}/.meteor/packages/ecmascript/.0.7.3.1f5h284++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/babel-core/lib/transformation/plugin.js:131:13:
   Plugin 0 specified in "foreign" provided an invalid property of
   "__wrapped__"
   at Plugin.init
  ${HOME}/.meteor/packages/ecmascript/.0.7.3.1f5h284++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/babel-core/lib/transformation/plugin.js:131:13)
   at Function.normalisePlugin
Brent Hoover
@zenweasel
Jun 06 2017 02:47
this is from a fresh reaction init?
ChanYu Chen
@j0214ack
Jun 06 2017 02:47
yes
maybe babel compiler is broken from the meteor part?
Maybe I should try uninstall meteor completely and try reaction init again
Brent Hoover
@zenweasel
Jun 06 2017 02:48
No, it shouldn’t be, everything should be self-contained. But it probably wouldn’t hurt to just wack your Meteor install
Yeah, give that a shot. I don’t know why that would cause a problem but still….
ChanYu Chen
@j0214ack
Jun 06 2017 03:09
UrAhhh nope, same error after uninstall meteor and recreate reaction init
Brent Hoover
@zenweasel
Jun 06 2017 03:10
Wow, that’s strange.
ChanYu Chen
@j0214ack
Jun 06 2017 03:12
trying adding meteor npm install
Brent Hoover
@zenweasel
Jun 06 2017 03:12
reaction init should be handling this for you
ChanYu Chen
@j0214ack
Jun 06 2017 03:14
You're right, this doesn't work haha
Jeremy Shimko
@jshimko
Jun 06 2017 03:15
have you installed all of the build requirements?
ChanYu Chen
@j0214ack
Jun 06 2017 03:16
yes~ I'm working on macOS with xCode installed, node version v6.9.5, and have changed the file limit
with brew, git and imagemagick
Jeremy Shimko
@jshimko
Jun 06 2017 03:16
what’s the error you got from the npm install?
ChanYu Chen
@j0214ack
Jun 06 2017 03:17
It's actually after starting MongoDB
=> Started MongoDB.
=> Errors prevented startup:

   While processing files with ecmascript (for target web.browser):

   /Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/babel-core/lib/transformation/plugin.js:131:13:
   Plugin 0 specified in "foreign" provided an invalid property of
   "__wrapped__"
   at Plugin.init
   (/Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/babel-core/lib/transformation/plugin.js:131:13)
   at Function.normalisePlugin
Jeremy Shimko
@jshimko
Jun 06 2017 03:17
so the npm install worked completely with no errors?
ChanYu Chen
@j0214ack
Jun 06 2017 03:17
yes
the complete msg stack is very long though
should I paste it all?
Jeremy Shimko
@jshimko
Jun 06 2017 03:18
if you want help, yes. :)
also, the output of reaction -v would be helpful
ChanYu Chen
@j0214ack
Jun 06 2017 03:20

reaction -v output:

Node: 6.9.5
NPM: 5.0.1
Meteor Node: 4.8.2
Meteor NPM: 4.5.0
Reaction CLI: 0.9.2
Reaction: 1.2.0
Reaction branch: master

Error msg:

(py27) ➜  reaction git:(master) reaction          

Using settings file at settings/dev.settings.json

Setting up plugin imports...

Setting up style imports...

[[[[[ ~/workspace/hhg/code/reaction ]]]]]

=> Started proxy.
=> A patch (Meteor 1.4.4.3) for your current release is available!
   Update this project now with 'meteor update --patch'.
=> Started MongoDB.
=> Errors prevented startup:

   While processing files with ecmascript (for target web.browser):

   /Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/babel-core/lib/transformation/plugin.js:131:13:
   Plugin 0 specified in "foreign" provided an invalid property of
   "__wrapped__"
   at Plugin.init
   (/Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/babel-core/lib/transformation/plugin.js:131:13)
   at Function.normalisePlugin
   (/Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/babel-core/lib/transformation/file/options/option-manager.js:152:12)
   at
   /Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/babel-core/lib/transformation/file/options/option-manager.js:184:30
   at Array.map (native)
   at Function.normalisePlugins
   (/Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/babel-core/lib/transformation/file/options/option-manager.js:158:20)
   at OptionManager.mergeOptions
   (/Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/babel-core/lib/transformation/file/options/option-manager.js:234:36)
   at
   /Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/babel-core/lib/transformation/file/options/option-manager.js:265:14
   at
   /Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/babel-core/lib/transformation/file/options/option-manager.js:323:22
   at Array.map (native)
   at OptionManager.resolvePresets
   (/Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/babel-core/lib/transformation/file/options/option-manager.js:275:20)
   at OptionManager.mergePresets
   (/Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/babel-core/lib/transformation/file/options/option-manager.js:264:10)
   at OptionManager.mergeOptions
   (/Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/babel-core/lib/transformation/file/options/option-manager.js:249:14)
   at OptionManager.init
   (/Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/babel-core/lib/transformation/file/options/option-manager.js:368:12)
   at File.initOptions
   (/Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/babel-core/lib/transformation/file/index.js:212:65)
   at new File
   (/Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/babel-core/lib/transformation/file/index.js:135:24)
   at Pipeline.transformFromAst
   (/Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/babel-core/lib/transformation/pipeline.js:69:16)
   at transform
   (/Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/meteor-babel/index.js:52:30)
   at compile
   (/Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/meteor-babel/index.js:70:14)
   at Cache.Cp.get
   (/Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/meteor-babel/cache.js:94:19)
   at Object.compile
   (/Users/chenzhanyou/.meteor/packages/ecmascript/.0.7.3.1d5hriy++os+web.browser+web.cordova/plugin.compile-ecmascript.os/npm/node_modules/meteor/babel-compiler/node_modules/meteor-babel/index.js:27:23)
   at Object.Babel.compile (packages/babel-compiler.js:48:24)
   at packages/babel-compiler.js:174:22
   at Function.time (/tools/tool-env/profile.js:305:10)
   at profile (packages/babel-compiler.js:217:20)
   at BabelCompiler.BCp.processOneFileForTarget
   (packages/babel-compiler.js:173:20)
   at BabelCompiler.<anonymous> (packages/babel-compiler.js:105:26)
   at Array.forEach (native)
   at BabelCompiler.BCp.processFilesForTarget
   (packages/babel-compiler.js:104:14)


=> Your application has errors. Waiting for file change.
Much appreciated! Thanks for help
Jeremy Shimko
@jshimko
Jun 06 2017 03:28
and you’re positive there were no issues with the meteor npm install?
ChanYu Chen
@j0214ack
Jun 06 2017 03:28
No, there were no issues
Jeremy Shimko
@jshimko
Jun 06 2017 03:30
What happens if you run it again? The only time I’ve ever seen that is when npm modules didn’t completely install.
ChanYu Chen
@j0214ack
Jun 06 2017 03:31
➜  reaction git:(master) meteor npm install
➜  reaction git:(master) {cursor}
it's all fine
or maybe it's npm5?
Jeremy Shimko
@jshimko
Jun 06 2017 03:34
considering nobody else is seeing this with the same version of npm, it feels unlikely, but it certainly doesn’t hurt to try. You already have 5.0.1, so go ahead and…
rm -rf node_modules
npm i
reaction
ChanYu Chen
@j0214ack
Jun 06 2017 03:43
npm i got no error, except node-pre-gyp build fallbacks to gyp, and few WARINING
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but npm-shrinkwrap.json was generated for lockfileVersion@0. I'll try to do my best with it!
npm WARN prefer global npm@2.15.12 should be installed with -g
npm WARN prefer global marked@0.3.6 should be installed with -g
npm WARN meteor-node-stubs@0.2.6 had bundled packages that do not match the required version(s). They have been replaced with non-bundled versions.
and after that reaction got same error
Brent Hoover
@zenweasel
Jun 06 2017 04:07
in that directory can you do git status?
ChanYu Chen
@j0214ack
Jun 06 2017 05:17
git stauts:
On branch master
Your branch is up-to-date with 'origin/master'.
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

    modified:   npm-shrinkwrap.json

no changes added to commit (use "git add" and/or "git commit -a")
and the git diff is so huge
some example diff:
 {
   "name": "reaction",
-  "version": "1.1.1",
+  "version": "1.2.0",
+  "lockfileVersion": 1,
   "dependencies": {
     "@reactioncommerce/authorize-net": {
-      "version": "1.0.8",
-      "from": "@reactioncommerce/authorize-net@>=1.0.8 <2.0.0",
-      "resolved": "https://registry.npmjs.org/@reactioncommerce/authorize-net/-/authorize-net-1.0.8.tgz"
+      "version": "https://registry.npmjs.org/@reactioncommerce/authorize-net/-/authorize-net-1.0.8.tgz",
+      "integrity": "sha1-eGQx7UGhUlp7IZRSA2DyEfcF6mg="
     },
     "42-cent-base": {
-      "version": "1.0.0",
-      "from": "42-cent-base@>=1.0.0 <2.0.0",
-      "resolved": "https://registry.npmjs.org/42-cent-base/-/42-cent-base-1.0.0.tgz"
+      "version": "https://registry.npmjs.org/42-cent-base/-/42-cent-base-1.0.0.tgz",
+      "integrity": "sha1-Yh0L6OzdgJaneHLK1cJ2NWB0k8g="
     },

...omitted

     "stripe": {
-      "version": "4.18.0",
-      "from": "stripe@>=4.16.0 <5.0.0",
-      "resolved": "https://registry.npmjs.org/stripe/-/stripe-4.18.0.tgz",
+      "version": "https://registry.npmjs.org/stripe/-/stripe-4.18.0.tgz",
+      "integrity": "sha1-iTDJisaQQ2WmCsTACm2eAJV3zFw=",
       "dependencies": {
         "qs": {
-          "version": "6.0.4",
-          "from": "qs@>=6.0.4 <6.1.0",
-          "resolved": "https://registry.npmjs.org/qs/-/qs-6.0.4.tgz"
+          "version": "https://registry.npmjs.org/qs/-/qs-6.0.4.tgz",
+          "integrity": "sha1-UQGdhHIMk5uCc36EVWp4Izjs6ns="
         }
       }
     },
     "supports-color": {
-      "version": "3.2.3",
-      "from": "supports-color@>=3.2.3 <4.0.0",
-      "resolved": "https://registry.npmjs.org/supports-color/-/supports-color-3.2.3.tgz"
+      "version": "https://registry.npmjs.org/supports-color/-/supports-color-3.2.3.tgz",
+      "integrity": "sha1-ZawFBLOVQXHYpklGsq48u4pfVPY="
     },
Brent Hoover
@zenweasel
Jun 06 2017 05:20
you’re not doing anything besides running reaction init and then reaction?
ChanYu Chen
@j0214ack
Jun 06 2017 05:21
reaction init => reaction => npm install => reaction => rm -rf node_modules && npm i => reaction
that's all I've done
Brent Hoover
@zenweasel
Jun 06 2017 05:23
right
how did you go about uninstalling Meteor?
ChanYu Chen
@j0214ack
Jun 06 2017 05:24
by following this: https://github.com/meteor/meteor#uninstalling-meteor
rm -rf ~/.meteor/ && sudo rm /usr/local/bin/meteor
Brent Hoover
@zenweasel
Jun 06 2017 05:24
seems right
ChanYu Chen
@j0214ack
Jun 06 2017 05:24
and then I didn't manually install it, I let reaction init install meteor
Brent Hoover
@zenweasel
Jun 06 2017 05:25
hmmmm
ChanYu Chen
@j0214ack
Jun 06 2017 05:26
Is it ok for npm to modify npm-shrinkwrap.json ?
Brent Hoover
@zenweasel
Jun 06 2017 05:26
that’s the only part that seems odd
can we try the whole thing again from the top?
ChanYu Chen
@j0214ack
Jun 06 2017 05:27
Do you mean this: reaction init => reaction => npm install => reaction => rm -rf node_modules && npm i => reaction?
and with meteor uninstalled ?
Brent Hoover
@zenweasel
Jun 06 2017 05:28
Nope. Uninstall Meteor, remove the previous reaction directories and do reaction init again
and then let’s stop there
ChanYu Chen
@j0214ack
Jun 06 2017 05:28
sure, but it's gonna take a while like 20 mins
Brent Hoover
@zenweasel
Jun 06 2017 05:28
we could probably skip the Meteor un/reinstall
ChanYu Chen
@j0214ack
Jun 06 2017 05:29
LOL, just did it
Brent Hoover
@zenweasel
Jun 06 2017 05:29
Ok, well it won’t hurt anything
ChanYu Chen
@j0214ack
Jun 06 2017 05:29
thanks again for your help and patience
okay, uninstalled meteor, deleted reaction dir, now going to reaction init
Brent Hoover
@zenweasel
Jun 06 2017 05:30
:+1:
ChanYu Chen
@j0214ack
Jun 06 2017 05:31
Since you mentioned npm modifying shrinkwarp is the only weird part, maybe I should try downgrading npm
Brent Hoover
@zenweasel
Jun 06 2017 05:32
well, I suppose anything is worth a try, but want to try changing one thing at a time
ChanYu Chen
@j0214ack
Jun 06 2017 05:33
Sure

despite this error

> node-pre-gyp install --fallback-to-build

node-pre-gyp ERR! Tried to download(404): https://github.com/kelektiv/node.bcrypt.js/releases/download/v1.0.2/bcrypt_lib-v1.0.2-node-v46-darwin-x64.tar.gz 
node-pre-gyp ERR! Pre-built binaries not found for bcrypt@1.0.2 and node@4.8.3 (node-v46 ABI) (falling back to source compile with node-gyp) 
  CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o
  CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o
  CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o
  SOLINK_MODULE(target) Release/bcrypt_lib.node
clang: warning: libstdc++ is deprecated; move to libc++ with a minimum deployment target of OS X 10.9 [-Wdeprecated]
  COPY /Users/chenzhanyou/workspace/hhg/code/reaction/node_modules/bcrypt/lib/binding/bcrypt_lib.node
  TOUCH Release/obj.target/action_after_build.stamp

reaction init successfully:


Reaction successfully installed!

To start your Reaction instance, just run: 

 cd reaction
 reaction
Brent Hoover
@zenweasel
Jun 06 2017 05:36
yeah, that’s normal
ChanYu Chen
@j0214ack
Jun 06 2017 05:37
Going to run reaction now
Brent Hoover
@zenweasel
Jun 06 2017 05:37
ok, try git status if you haven’t started reaction first
ChanYu Chen
@j0214ack
Jun 06 2017 05:38
I've started, but i'm pretty sure it's clean since my terminal plugin didn't indicate uncommit changes
Brent Hoover
@zenweasel
Jun 06 2017 05:38
k
do you run pyenv?
or virtualenv?
ChanYu Chen
@j0214ack
Jun 06 2017 05:39
i have anaconda
Brent Hoover
@zenweasel
Jun 06 2017 05:39
oh boy
ChanYu Chen
@j0214ack
Jun 06 2017 05:40
We got it!?
Brent Hoover
@zenweasel
Jun 06 2017 05:40
No, sorry
didn’t mean to get you excited
ChanYu Chen
@j0214ack
Jun 06 2017 05:40
LOL, okay
Brent Hoover
@zenweasel
Jun 06 2017 05:42
your shell was showing the python version so I thought that might be relevant, although a long shot
pyenv/virtualenv do mess around with pathing
ChanYu Chen
@j0214ack
Jun 06 2017 05:44
I'm not very familiar with python though, don't know if there's a way to cancel anoconda's behaviour
Brent Hoover
@zenweasel
Jun 06 2017 05:44
I don’t think it’s relevant tbh
but who knows
ChanYu Chen
@j0214ack
Jun 06 2017 05:45
still building, if it failed again I'd try downgrading npm first
Brent Hoover
@zenweasel
Jun 06 2017 05:45
yeah, I want to find out at what stage it’s modifying the shrinkwrap file
ChanYu Chen
@j0214ack
Jun 06 2017 05:47
failed again, and git status shows:
➜  reaction git:(master) git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working tree clean
Brent Hoover
@zenweasel
Jun 06 2017 05:48
RAgggh
so here’s what I have as far as versions:
Node: 7.10.0
NPM: 4.2.0
Meteor Node: 4.8.2
Meteor NPM: 4.5.0
Reaction CLI: 0.9.2
Reaction: 1.2.0
Reaction branch: master
Docker: 17.03.1-ce
it looks to me like our Meteor Node and NPM are identical which I would expect
so you could try downgrading NPM to that same version?
ChanYu Chen
@j0214ack
Jun 06 2017 05:50
you mean 4.2.0 or meteor's 4.5.0 ?
Brent Hoover
@zenweasel
Jun 06 2017 05:50
4.2.0
the global npm
ChanYu Chen
@j0214ack
Jun 06 2017 05:51
okay, let me google how first haha, I'm using nvm
Brent Hoover
@zenweasel
Jun 06 2017 05:51
hmmm
ChanYu Chen
@j0214ack
Jun 06 2017 05:52
seemsnpm install -g npm@4.2.0 would work, wait a sec
yay, worked
reaction -v:
Node: 6.9.5
NPM: 4.2.0
Meteor Node: 4.8.2
Meteor NPM: 4.5.0
Reaction CLI: 0.9.2
Reaction: 1.2.0
Reaction branch: master
now running reaction (same old dir)
Same error.
Now trying make a new one:
reaction init && cd reaction && reaction
ChanYu Chen
@j0214ack
Jun 06 2017 06:05
still same error
Brent Hoover
@zenweasel
Jun 06 2017 06:06
can you try not using nvm? Are you using that for other things?
ChanYu Chen
@j0214ack
Jun 06 2017 06:07
using it just for convenience, I could try get rid of that
Brent Hoover
@zenweasel
Jun 06 2017 06:10
I mean, if it’s going to screw up your whole dev environment I am not sure it’s worth it. But it could be messing with it somehow. I don’t use it myself and when I did I had troubles.
ChanYu Chen
@j0214ack
Jun 06 2017 06:14
It's fine, this machine is only for some small side project
Brent Hoover
@zenweasel
Jun 06 2017 06:15
I can’t believe you are the first person to be using nvm tho, it must be pretty common I would think
ChanYu Chen
@j0214ack
Jun 06 2017 06:24
no, it's not about nvm, I deleted it and download node from here: https://nodejs.org/en/download/, get npm upgrade to v4.2.0, then reaction init && cd reaction && reaction same error
Brent Hoover
@zenweasel
Jun 06 2017 06:25
yh, then I am officially stumped
the only time I have seen that error before is when meteor npm install has not been run.
and the only thing weird about your setup (from my perspective) is that you tried to upgrade Meteor. But un/install should have taken care of that
ChanYu Chen
@j0214ack
Jun 06 2017 06:30
the only thing I haven't tried now is anoconda
maybe tomorrow lol
Thanks a lot anyway! Really feel supported
Vigy
@vigyano
Jun 06 2017 06:57
Thanks @kieckhafer for response.
ushadev
@ushadev
Jun 06 2017 07:25
Having issue in products gallery with 'SoldOut' badge. i have products gallery and sub tags tag1, tag2, tag3 and tag4.(so i have gallery, tag1, tag2. tag3, tag4). now while adding new products i select gallery and tag1 for a specific product and inventory quantity >= 1. in the tag1 products view. there is no Sold Out badge but in the gallery products view there is a sold Out badge(though the the inventory > 0) this happens in admin mode. Why is this happening?
Brent Hoover
@zenweasel
Jun 06 2017 10:09
does it only happen in admin mode?
Robin Winkelewski
@w9n
Jun 06 2017 10:17
im very frustrated with the example plugin... adding new Products and the landing page does not work with the plugin - i also could not deactivate the plugin by modifying the register.js or the Packages document, only removing the files works. Thats the frontend exception
TypeError: Cannot read property '_id' of undefined
    at productGrid.js:26
    at modules.js?hash=5bcb00d…:76748
    at modules.js?hash=5bcb00d…:76212
    at baseForOwn (modules.js?hash=5bcb00d…:76154)
    at modules.js?hash=5bcb00d…:76248
    at baseFilter (modules.js?hash=5bcb00d…:76747)
    at filter (modules.js?hash=5bcb00d…:76720)
    at Blaze.TemplateInstance.<anonymous> (productGrid.js:25)
    at blaze.js:3398
    at Function.Template._withTemplateInstanceFunc (blaze.js:3744)
Brent Hoover
@zenweasel
Jun 06 2017 10:18
To decativate the plugin you can just rename the directory with a period in front of it
so do the products that are imported work correctly and just not products that you have created by hand?
Robin Winkelewski
@w9n
Jun 06 2017 10:20
when im loged in as admin the landing page does not load at all - as no user it does not load all products
Brent Hoover
@zenweasel
Jun 06 2017 10:21
Are you using the example plugin from the repository or a version you have created from the tutorial?
Robin Winkelewski
@w9n
Jun 06 2017 10:22
i tried master and Meteor 1.5 plus the example git plugin as master branch
Brent Hoover
@zenweasel
Jun 06 2017 10:22
you mean the Meteor 1.5 branch?
Robin Winkelewski
@w9n
Jun 06 2017 10:22
yep
Brent Hoover
@zenweasel
Jun 06 2017 10:23
I don’t know if the example-plugin works with that or not, I haven’t tested it yet
Robin Winkelewski
@w9n
Jun 06 2017 10:23
i tried the master at the beginning with the same error
Brent Hoover
@zenweasel
Jun 06 2017 10:23
I only test the example-plugin with master
Ok, let me pull it up right now and see what’s up
Robin Winkelewski
@w9n
Jun 06 2017 10:24
yes i added three products published them -> installed the plugin
Brent Hoover
@zenweasel
Jun 06 2017 10:28
Yeah, I see what you are seeing
Robin Winkelewski
@w9n
Jun 06 2017 10:29
it also fails in the tag view, only showing some products with the same error
Brent Hoover
@zenweasel
Jun 06 2017 10:30
Ok
ushadev
@ushadev
Jun 06 2017 10:34
@zenweasel yes. it happens in admin mode only.
Brent Hoover
@zenweasel
Jun 06 2017 10:35
Yeah, I see that
I see the same issue without adding any products. Just the stock one.
Robin Winkelewski
@w9n
Jun 06 2017 10:40
i tried to debug what product data is passed in the function but only get the an object with the same id when i breakpoint in chrome
Robin Winkelewski
@w9n
Jun 06 2017 10:46
i just reseted the db and it worked with the stock product until i added a new one
Brent Hoover
@zenweasel
Jun 06 2017 10:46
if I change if (products) to if (products.length) that seems to stop the errors. It’s getting an empty array there
Robin Winkelewski
@w9n
Jun 06 2017 10:49
ill give it a try - still fighting with the debugger
Brent Hoover
@zenweasel
Jun 06 2017 10:50
still confused as to how the example-plugin could be causing this issue :confused:
Brent Hoover
@zenweasel
Jun 06 2017 11:00
this whole product grid is going to be replaced in a couple of days
Robin Winkelewski
@w9n
Jun 06 2017 11:05

i would guess here https://github.com/reactioncommerce/reaction-example-plugin/blob/master/client/templates/products/productsLanding.js#L91

the failing part get called inside this event

Template.productGrid.events({                                                                                          //
  "click [data-event-action=loadMoreProducts]": function (event) {                                                     // 88
    event.preventDefault();                                                                                            //
    loadMoreProducts();                                                                                                // 88
  },
Brent Hoover
@zenweasel
Jun 06 2017 11:07
yeah, good call. I think that that probably needs to get changed to this.products.set(products.fetch());
The if (products) is true because products is a cursor, but it should be an empty array, which would be false
Robin Winkelewski
@w9n
Jun 06 2017 11:09
seems to work!
Brent Hoover
@zenweasel
Jun 06 2017 11:11
Let me test it a little more and I will put in a PR for it. But at least it’s working for you now
Robin Winkelewski
@w9n
Jun 06 2017 11:16
yep only added fetch() and seems to work flawless now, thanks :) I guess there is no admin ui element yet to delete an article fully yet?
Robin Winkelewski
@w9n
Jun 06 2017 11:31
the footer in the example plugin does also not sit on bottom because the main app is not overflow auto
juandanceswild
@juandanceswild
Jun 06 2017 14:28
@zenweasel @spencern thanks for your help guys! Yea, the UI was telling be that the item was published/there was nothing to publish, but the terminal was giving me the error that the product needed a label (which it had). In the end, the problem was that the variant wasn’t visible and that’s why it wasn’t posting. This is probably a bug still.
juandanceswild
@juandanceswild
Jun 06 2017 15:45
I’ve been consistently getting an error that breaks the local server of my reaction instance after a few minutes…
/private/var/folders/85/zjn11px90_9b66qzgkkk5q780000gn/T/shelljs_d12b50db97e1faf7e23b:10 fs.writeFileSync(fname, err.code.toString()); ^ TypeError: Cannot read property 'toString' of null at /private/var/folders/85/zjn11px90_9b66qzgkkk5q780000gn/T/shelljs_d12b50db97e1faf7e23b:10:37
Jeremy Shimko
@jshimko
Jun 06 2017 16:05
@juandanceswild Yep, that’s unfortnately a known (and quite old) issue with Meteor. I think it might be something to do with memory usage, but there’s no clear answer on it yet. On the upside, that only effects your development environment. Meteor doesn’t exist anymore in a production deployment, so neither does that problem.
reactioncommerce/reaction#1590
Most likely related: meteor/meteor#8648
juandanceswild
@juandanceswild
Jun 06 2017 16:24
got it, thanks! @jshimko
Sophie He
@sophiehe
Jun 06 2017 20:04
If you're just getting started, here is a video tutorial on how to install Reaction for macOS: https://youtu.be/PkFDX8NWskY
Kenneth Beartusk
@beartusk
Jun 06 2017 20:14
The "Load More Products" button doesn't seem to be working for me at the bottom of my product pages. As a non-admin I can't view about half the items that should be in there. But, I can view them if I type the correct URL in (e.g. http://localhost:3000/sweet-grass/product/gold-sample-package). What am I missing here?