These are chat archives for reactioncommerce/reaction

11th
Jul 2018
Patrick Newell
@pnewell4_twitter
Jul 11 2018 02:33 UTC
does this look familiar to anyone who has upgraded to 1.13.1?
events.js:183░░░░░░⸩ ⠇ extract:react-textarea-autosize: sill extract prerender-node@2.7.4
      throw er; // Unhandled 'error' event
      ^

Error: write after end
    at writeAfterEnd (_stream_writable.js:236:12)
    at PassThrough.Writable.write (_stream_writable.js:287:5)
    at PassThrough.Writable.end (_stream_writable.js:563:10)
    at ReadEntry.entry.on (/Users/pmn/.meteor/packages/meteor-tool/.1.7.0_3.w52zoc.6jwaf++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/pacote/lib/extract-stream.js:19:41)
Patrick Newell
@pnewell4_twitter
Jul 11 2018 02:43 UTC
(that's an error I see when running reaction reset -y)
here's one I get from reaction run:
=> Errors prevented startup:                  

   While processing files with ecmascript (for target web.browser):
   /Users/pmn/code/personal/brewline/reserve-reaction/node_modules/@babel/preset-stage-2/lib/index.js:101:11: [BABEL]
   /Users/pmn/code/personal/brewline/reserve-reaction/imports/plugins/custom/reaction-connectors-untappd/lib/collections/schemas/index.js: The new decorators proposal is
   not supported yet. You must pass the `"decoratorsLegacy": true` option to @babel/preset-stage-2 (While processing: "base$3")
and the file referenced (index.js) is simply:
export * from "./untappdConnect";
// EOF
Brent Hoover
@zenweasel
Jul 11 2018 02:53 UTC
I think you need to make a change to your package.json babel config
          [
            "@babel/preset-stage-2",
            {
              "decoratorsLegacy": true
            }
          ]
nickthejagger
@nickthejagger
Jul 11 2018 02:57 UTC
@zenweasel how to run it properly in digitalocean then? i tried docker but it's just give me blank webpage
Brent Hoover
@zenweasel
Jul 11 2018 02:59 UTC
Not sure. But I don’t think it’s a Reaction problem
nickthejagger
@nickthejagger
Jul 11 2018 02:59 UTC
@zenweasel so how to run it not as root user?
Brent Hoover
@zenweasel
Jul 11 2018 03:00 UTC
there’s no reason to run it as root
Those instructions cover deploying to Digital Ocean specifically
nickthejagger
@nickthejagger
Jul 11 2018 03:13 UTC
@zenweasel i run it as normal server not as docker engine unfortunately.
Brent Hoover
@zenweasel
Jul 11 2018 03:23 UTC
Sorry, I don’t know how else I can help you. You need to just create a user that is not root and run the app using that. Deploying something as root is generally bad practice anyway since that user has access to all of your server.
I would strongly suggest that you move to a docker-based deployment. That is all we support
nickthejagger
@nickthejagger
Jul 11 2018 03:23 UTC
okay then.
like i said before. the docker compose up give me blank website. no error reported
Brent Hoover
@zenweasel
Jul 11 2018 03:24 UTC
It’s something with your particular installation though. It’s not a reaction problem
I am testing a cluster right now with 64 servers running Reaction
nickthejagger
@nickthejagger
Jul 11 2018 03:48 UTC
icic will check again for sure
nickthejagger
@nickthejagger
Jul 11 2018 04:06 UTC
okay trying docker once again. and get this error ERROR: Service 'devserver' failed to build: Unknown flag: chown
nickthejagger
@nickthejagger
Jul 11 2018 04:16 UTC
same error when built custom image Step 4/20 : COPY --chown=node package-lock.json $APP_SOURCE_DIR/
nickthejagger
@nickthejagger
Jul 11 2018 05:43 UTC
sorry for the fuss. i'm using docker from snap. and for whatever reason it's show error
Janus Reith
@janus-reith
Jul 11 2018 08:57 UTC
Did anyone try to extend the Product Variant schema in 1.13.1?
Somehow my custom fields are only published to the admin user, and skipped for other clients.
I described my issue here: reactioncommerce/reaction-swag-shop#68
Did anyone manage to do that in 1.13.1 and might give me a hint what is missing?
Patrick Newell
@pnewell4_twitter
Jul 11 2018 20:30 UTC
anyone seeing an error like this?:
Error: Cannot find module 'stream'
    at makeMissingError (modules-runtime.js?hash=59942621baf2d3ff23916a0f601008fd2e310b63:241)
    at require (modules-runtime.js?hash=59942621baf2d3ff23916a0f601008fd2e310b63:251)
    at bunyan.js (modules.js?hash=89619d047c11b9e919b2c225e1120c190d5696d4:64239)
    at fileEvaluate (modules-runtime.js?hash=59942621baf2d3ff23916a0f601008fd2e310b63:349)
    at require (modules-runtime.js?hash=59942621baf2d3ff23916a0f601008fd2e310b63:248)
    at main.js (modules.js?hash=89619d047c11b9e919b2c225e1120c190d5696d4:63935)
    at fileEvaluate (modules-runtime.js?hash=59942621baf2d3ff23916a0f601008fd2e310b63:349)
    at require (modules-runtime.js?hash=59942621baf2d3ff23916a0f601008fd2e310b63:248)
    at index.js (index.js:1)
    at fileEvaluate (modules-runtime.js?hash=59942621baf2d3ff23916a0f601008fd2e310b63:349)
(in the client)
...which comes from /node_modules/@reactioncommerce/logger/node_modules/bunyan/lib/bunyan.js
I just went to version 1.13.1, if that is at all helpful.
thanks!
Loan Laux
@loanlaux
Jul 11 2018 21:13 UTC
Never seen this one @pnewell4_twitter
Patrick Newell
@pnewell4_twitter
Jul 11 2018 21:15 UTC
thanks Loan. trying a reaction reset -y one. more. time.
Loan Laux
@loanlaux
Jul 11 2018 21:15 UTC
We're with you on this one :grimacing:
Patrick Newell
@pnewell4_twitter
Jul 11 2018 21:15 UTC
c'mon npm! do your thing!