These are chat archives for reactioncommerce/reaction
Hi all! I'm writing unit tests for a GraphQL mutation that calls
Reaction.Email.send at some point. As part of my tests, I want to make sure the email is sent. Since my test file lives at the resolver level (in the
no-meteor folder), I don't have access to
meteor/practicalmeteor:sinon, which I would usually use to create a sandbox, stub
Reaction.Email.send and expect it to be called.
Two questions: can I use
sinon from a
no-meteor test file? If I can't, then how can I make sure this mutation sends this email?
RCHeadercomponent with Reaction's
registerComponentmethod. Give it the name
levelKidsPDPSimpleand remove the
[plugin]/client/templates/directory altogether. The React component will be directly rendered instead of being wrapped in a Blaze template. It's cleaner and less prone to errors popping up.
product-detail-simpleplugin takes over Reaction's default. Use the
priority: 0property in your registry entries (where your routes are defined).
Not only will you comply and get frequent updates, but your site's performance will improve by a lot (especially TTFP) and your developer experience will be much better. With Reaction 1.x, your workflow probably suffers from high rebuild times, which are basically gone for the front-end side on 2.x.
I would highly recommend switching if you're not far into development of this project.
@babel/plugin-proposal-json-stringscannot be found
docker-composeunless for specific situations.
reaction-next-startkit, I just need to run
reactionafter running a
makein the parent folder
reactionshould start by itself when you use the
makecommand. Doesn't it?
docker psI know what is causing this. Did you change your memory allocation in Docker's control panel?
makecommand and then running
reaction --port 9001command with a different port. but this then uses the
reactionand not the Next+GraphQL
makecommand is supposed to launch all the services. You shouldn't have to launch
reactionmanually. But if you haven't allocated more memory to Docker, it's highly probable that
reactionfails during the build phase. Hence my question — did you change your Docker memory allocation settings?
makethat it couldn't get the FE app up?
reaction-next-starterkit_webservice is not getting up
make init-...for the same
docker psright after your
docker logs -f [container_id]to see what's going on behind the scenes.
make cleanand start over.
yarn installwasn't entirely successful and it kept running for some reason, leaving you with an incomplete
makeis still in progress
yarn install v1.12.3 [1/4] Resolving packages... [2/4] Fetching packages... info firstname.lastname@example.org: The platform "linux" is incompatible with this module. info "email@example.com" is an optional dependency and failed compatibility check. Excluding it from installation. [3/4] Linking dependencies... warning " > firstname.lastname@example.org" has unmet peer dependency "babel-runtime@^6.20.0". warning " > email@example.com" has incorrect peer dependency "react@^15.0.0".
[4/4] Building fresh packages... warning Ignored scripts due to flag.