CHANGELOG.md

v3.11.1

Reaction v3.11.1 adds minor bug fixes and contains no breaking changes since v3.11.0.

Fixes

• fix: write integration test for create shop (#6318)
• Run rs.initiate() to start replication on clean mongo boot (#6317)

Chores

• chore: adding git hooks for commit-msg (#6321)

v3.11.0

Reaction v3.11.0 adds minor enhancements, fixes bugs and contains no breaking changes since v3.10.0.

Notable changes

Fixed image uploads

Fixed issues causing image upload to fail.

Fixes

• fix: Get product image uploads working again (#6309)

Refactors

• refactor: preserve symlinks in docker debug npm scripts (#6302)

Chores

• chore: Update @reactioncommerce dependencies (#6296)
• chore: Update api-plugin-shops (#6295)
• chore: update api-plugin-accounts package (6312)

Contributors

Thanks to @loan-laux and @balibebas for contributing to this release! 🎉

v3.10.0

Reaction v3.10.0 adds minor features and performance enhancements, and contains no breaking changes since v3.9.0

Notable changes

Update node from v12.x to v14.x

Update Reaction to current stable node for general maintenance.

Please note that node's ES Modules support is stable, but still experimental. While we are not aware of any specific breaking changes or issues, some CommonJS/ES Modules refactoring may be necessary in some installations.

Features

feat: update to nodejs v14 (#6292)

v3.9.0

Reaction v3.9.0 adds minor features and performance enhancements, and contains no breaking changes since v3.8.0

Chores

chore: update simple authorization plugin (#6274) chore: Update accounts package (#6269) chore: use yalc for package link and unlink (#6266) chore: updated api plugins (#6265) chore: fix package link script issues (#6251)

Contributors

Thanks to @loan-laux for contributing to this release! 🎉

v3.8.0

Reaction v3.8.0 adds minor features and performance enhancements, and contains no breaking changes since v3.7.1

Notable changes

Add package link and unlink scripts for easier testing of plugins

bin/package-link and bin/package-unlink allow you to test local plugins easily and efficiently, no longer needing you to npm link packages or adjust your docker-compose.yml file.

Update various api-plugins

• api-core (Release notes)
• api-plugin-accounts (Release notes)
• api-plugin-carts (Release notes)
• api-plugin-orders (Release notes)
• api-plugin-shops (Release notes)
• api-plugin-taxes-flat-rate (Release notes)
• api-utils (Release notes)

Chore

• chore: add package link and unlink scripts (#6238)
• chore: fix package link script issues (#6251)

Fixes

• chore: fix package link script issues

v3.7.1

Reaction v3.7.1 adds a bug fix and contains no breaking changes since v3.7.0

Notable changes

Fix API Docker image

Updates Dockerfile to copy new plugins.json into the Docker image.

Fixes

• fix: copy plugins.json into prod image (#6244)

v3.7.0

Reaction v3.7.0 adds minor features and performance enhancements, and contains no breaking changes since v3.6.0.

Notable changes

Moves API Core into its own plugin

API core is now its own plugin which provides the ReactionAPICore class. Use this to build a NodeJS microservice that is compatible with the Reaction Commerce platform, or to build your main Reaction Commerce API if you don't want to start by forking this project.

Finishes moving all plugins into their own npm packages

All remaining plugins which were not moved previous to this release have now been moved out of this project and into their own npm plugins.

Features

• feat: reaction as library (#6155)

Refactors

• refactor: use npm package for taxes plugin (#6228)
• refactor: move shipments-flat-rate plugin to npm (#6199)
• refactor: move taxes-flat-rate plugin to npm (#6198)
• refactor: use npm package for inventory plugin (#6226)
• refactor: use npm package for simple-pricing plugin (#6225)
• refactor: move shipments plugin to NPM package (#6224)
• refactor: use npm package for files plugin (#6217)
• refactor: move surcharges plugin to NPM package (#6223)
• refactor: use npm package for products plugin (#6220)
• refactor: move discounts plugin to NPM package (#6216)
• refactor: use npm package for simple-inventory plugin (#6222)
• refactor: move email-smtp plugin to NPM package (#6218)
• refactor: move email-templates plugin to NPM pkg (#6219)
• refactor: move payments plugin to NPM package (#6221)
• refactor: move payments-stripe plugin to npm (#6161)
• refactor: use npm package for carts plugin (#6215)
• refactor: move email plugin to npm (#6200)
• refactor: move orders plugin to NPM (#6214)
• refactor: move notifications plugin to npm (#6211)
• refactor: move job-queue plugin to npm (#6197)
• refactor: use npm package for tags plugin (#6212)

Chores

• chore: update renamed plugins (#6236)
• chore: update plugins (#6235)
• chore: remove unused npm packages (#6229)
• chore: update api-core (#6227)

v3.6.0

Reaction v3.6.0 adds minor features and performance enhancements, fixes bugs, and contains no breaking changes since v3.5.0.

Notable changes

Addresses hidden items in cart and checkout

Fixes a bug which was causing cart and checkout to fail if an item was hidden after it was added to cart

Moves eight plugins into their own npm packages

accounts, address-validation, address-validation-test, catalogs, i18n, settings, simple-schema and shops plugins have been moved from internal plugins, to npm install packages.

Refactors

• refactor: use npm package for settings plugin (#6203)
• refactor: move simple-schema plugin to npm (#6202)
• refactor: use npm package for shops plugin (#6201)
• refactor: move catalogs plugin to npm (#6196)
• refactor: move i18n service to npm (#6193)
• refactor: move address-validation service and address-validation-test plugin to npm (#6186)
• refactor: move accounts plugin to npm (#6189)

Fixes

• fix: find catalog product regardless of visibility (#6089)

Chores

• chore: update graphql-schema-linter (#6192)

v3.5.0

Reaction v3.5.0 adds minor features and performance enhancements, fixes bugs, and contains no breaking changes since v3.4.0.

Notable changes

Moves three plugins into their own npm packages

discount-codes, sitemap-generator and translations plugins have been moved from internal plugins, to npm install packages.

Price field has been deprecated on Product Variants and Options

A new pricing field has been added to Product and ProductVariant types, and price has been deprecated, to keep field consistant across packages and product types.

Features

• feat: support passing product data with createProduct and createProductVariant (#6150)

Refactors

• refactor: deprecate bin/token script (#6183)
• refactor: move sitemap generator plugin to npm (#6144)
• refactor: move translations plugin to npm (#6160)
• refactor: npm discount codes (#6157)
• refactor: filter out variant media from product media query (#6165)

Fixes

• fix: adds new pricing field to product variants in order to correctly display prices (#6159)
• fix: Update getAuthToken for ES6 modules (#6156)

Chores

• chore: issue template update (#6158)
• chore: Update security deps (#6190)

Docs

• docs: Fix simple typo, epxect -> expect (#6188)

Contributors

Thanks to @timgates42 for contributing to this release! 🎉

v3.4.0

Reaction v3.4.0 adds minor features and performance enhancements, and contains no breaking changes since v3.3.0.

Notable changes

Moves two plugins into their own npm packages

navigation and payments-example plugins have been moved from internal plugins, to npm install packages.

Adds additional fields to updateShop mutation

updateShop mutation has been expanded to allow updating of more Shop related settings via the GraphQL API

Refactors

• refactor: add missing fields to updateShop mutation (#6146)
• refactor: move navigation plugin into npm (#6118)
• refactor: move payments-example plugin to npm package (#6142)

Fixes

• fix: variant clone produces null and undefined values (#6149)

Contributors

Thanks to @trojanh for contributing to this release! 🎉

v3.3.0

Reaction v3.3.0 adds minor features and performance enhancements, and contains no breaking changes since v3.2.0.

Notable changes

Roles and Permissions code has finished moving out of the API

Remaining role and permissions related code has been moved of the API and into the simple-authorization plugin, which makes it easier to swap this plugin for a custom authorization service.

Features

• feat: various updates for product editor (#6141)

Refactors

• refactor: allow all users with token to view order (#6092)
• refactor: move roles and group.permissions code from account plugin to simple-auth plugin (#6111)
• refactor: add translation strings for settings form (#6097)

v3.2.0

Reaction v3.2.0 adds minor features and performance enhancements, and contains no breaking changes since v3.1.0.

Notable changes

Introduces Federated Gateway capabilities for the API

Introduces Gateway capability, which allows for the API to be a participant on the Federated Gateway.

Moves two plugins into their own npm packages

simple-authorization and system-information plugins have been moved from internal plugins, to npm install packages.

Features

• feat: add gateway capabilities to API (#6100)
• feat: add updateProductsVisibility mutation (#6104)

Refactors

• refactor: move system information plugin to npm (#6105)
• refactor: replace internal authentication plugin with NPM installed plugin-authentication (#6108)

Chores

• chore: update plugin-simple-authorization package (#6110)

v3.1.0

Reaction v3.1.0 adds minor features and performance enhancements, fixes bugs, and contains no breaking changes since v3.0.0.

Notable changes

Moves our first plugin into its own npm package

Moves our simple-authorization plugin (formerly legacy-permission) into it's own npm package to set up the pattern of installing Reaction API plugins from npm.

Features

• feat: move legacy permissions into npm package (#6096)

Fixes

• fix: Add variant tax fields to schema (#6098)

v3.0.0

We're excited to introduce version 3.0.0 (v3.0.0) of the Reaction Commerce GraphQL API (hereby referred to as "The Reaction API"). In this version, we've expanded the existing GraphQL API to include administrative and operator functionality, eliminated the Meteor framework from the Reaction API, split the Reaction Admin UI and the identity provider into separate services, added support for plugins as NPM packages, and improved automated integration testing for the Reaction API.

Notable Changes

Reaction API is now fully headless

The reactioncommerce/reaction repo exclusively hosts the Reaction API in v3.0.0. This Reaction API now has full GraphQL coverage of the functionality that was previously provided by Meteor. In v2 we introduced GraphQL into the Reaction API for storefronts. Now the Reaction API includes GraphQL coverage for administrative and operator functionality. This enables the creation of custom UI for operating a shop using Reaction Commerce.

Plugins as NPM Packages

The Reaction API plugin system has changed a lot - primarily because the Reaction API runs as a Node.js application instead of a Meteor application. It's now possible and recommended to write plugins as NPM packages. See our docs on plugins in Reaction 3.x for details.

Permissions system overhaul

Permissions of a Reaction Account are now exclusively determined by the permissions of the Group (or Groups) the Account belongs to.

Previously, roles (renamed permissions) were attached to a user by querying the single Group a user belonged to, and copying the group permissions over to the user account. Permissions were then checked against the user.roles object. If there was ever an update to the permissions a group was allowed, every user in the group needed to be updated.

In v3.0.0, Accounts are now allowed to be added to more than one group, and permissions are checked by querying the Groups the user belongs too, aggregating all permissions all of these groups, and then checking against this list of permissions. If a group is ever updated, each individual account no longer needs to be updated.

Improved Integration Test Coverage

We've written many integration tests for our Reaction API. See this GitHub ticket for a full list of new integration tests. While we've made huge strides here to improve test coverage, there is still room for improvement here. We'd welcome contributions that improve our test coverage!

Removed Meteor from the Reaction API

Improving developer experience has been high on the list of priorities for quite a while. We've made significant improvements to startup, restart, and build times for the reaction project by removing Meteor. In doing this we've also updated to version 12 of Node.js, which is in Active LTS status.

Reaction Admin has a new home

With this release, we are also introducing a beta of Reaction Admin, now a standalone application. We've moved the codebase for the Admin UI into a separate repository - reactioncommerce/reaction-admin. It's important to note that while this is the official v3.0.0 release of the Reaction API, we're keeping the beta tag on Reaction Admin for now.

Our focus and effort for this release has primarily been on readying our full GraphQL Reaction API. We're keeping Reaction Admin in beta because it uses Meteor under the hood for builds and there are still a few Meteor APIs left in the codebase. The future Reaction Admin UI will use the Reaction API exclusively. The Reaction Admin project will be in beta beyond the v3.0.0 release of Reaction API. We suggest careful consideration before copying any patterns found in the Reaction Admin project while it still has the beta tag. There are sections where it consumes the Reaction API and other sections that still use patterns from when the Admin UI was part of the monolithic Meteor application.

New identity provider service: Reaction Identity

This release moves the identity provider for Reaction into a separate service - reactioncommerce/reaction-identity. Reaction Identity is the user interface and server for identity management, including user registration, login, logout, and password change. It works together with reaction-hydra to enable OAuth2 flows.

Independent Releases

v3.0.0 is a coordinated release across all of Reaction's open source projects. Following this release, we will release Reaction Commerce projects independently. For example, if there are fixes or improvements made to the Example Storefront or to the API, they can be released without bumping the version of every other project. Reaction Development Platform will continue to be bumped with each release of a Reaction Commerce project.

Mongo 4

Mongo version 4.0+ is now required. Mongo 4 introduces multi-document transactions. Requiring Mongo 4+ means that services and plugins can start using transactions where necessary to ensure better data integrity.

Default to running public docker images

The docker-compose.yml file in each project now uses public images rather than building an image. This drastically speeds up the initial startup time in development, and makes the application run smoother in development. When you're ready to start developing, you'll need to switch over to using the docker-compose.dev.yml file in the project you're wanting to develop - see for example: reaction/docker-compose.dev.yml).

Migrations

The migration tool in Reaction v2.x depended on Meteor and was built into the Reaction monolith. For v3.0.0, we've moved to a new CLI migration tool for MongoDB. We weren't planning to write Migrator, but we couldn't find anything that met all of our MongoDB migration needs. Although we built Migrator for Reaction Commerce, it is a general purpose MongoDB data migration tool that you can use for any project. See the project page for details on why we decided to build our own and to learn how to use the new migration tool. We've got an example project that you can use to get started. There's also an npm package that can ensure your database has migrated to the correct version before running any commands.

How to get started with Reaction v3.0.0

Our (recently renamed) reactioncommerce/reaction-development-platform project is still the best place to start if you want to check out what Reaction has to offer or start developing for Reaction. If you're experienced with Reaction already check-out our Upgrade Guide. If you've got a plugin you'd like to upgrade, read our guide for updating a 2.x API plugin to work with Reaction API 3.x.

Features

• feat: Add Accounts GraphQL query to find non-admin accounts (#5848)
• feat: add addAccountEmailRecord mutation and corresponding integration (#5813)
• feat: Add Babel config to make Jest tests work (#5728)
• feat: add checkPermissions function (#5727)
• feat: Add createNavigationTree mutation & its tests (#6023)
• feat: add delete action to account managers policy (#6024)
• feat: add email templates query (#5811)
• feat: add graphql equivalent of create group (#5850)
• feat: Add updateAccountGroup mutation (#6016)
• feat: add updateProduct and updateProductVariant mutations for 3.0 (#5768)
• feat: add updateProductVariantPrices mutation to API (#5910)
• feat: addCartItems mutation (#5814)
• feat: adds integration test for generateSitemaps mutation (#5995)
• feat: Allow remoteURL in MediaRecordInfo schema (#6074)
• feat: authentication plugin; drop support for meteor-login-token header (#5999)
• feat: authorization plugin & checkPermissions functionality (#5724)
• feat: Better internal context design (#6020)
• feat: change graphql route (#6027)
• feat: Create updateAccount GraphQL mutation (#6067)
• feat: GQL discount & discount codes plugins (#5800)
• feat: GQL Email (core/email) (#5793)
• feat: GQL products & product query (#5818)
• feat: GQL Tags (core/tags) (#5786)
• feat: GQL tax rates (#5774)
• feat: GQL Templates (core/templates) (#5792)
• feat: Product/Variant GQL fixes (#6079)
• feat: pt-BR translation for reaction-orders. (#6004)
• feat: pt-BR translation for reaction-tags. (#5997)
• feat: retry initial MongoDB connections (#5807)
• feat: Shipping (flatRateFulfillmentMethods) query (#5844)
• feat: Tag query improvements (#5783)
• feat: Update brand assets and parcel size on shop (GQL) (#5846)
• feat: update groups permission with migration (#6086)
• feat: update updateShop mutation to set all necessary settings (#5804)
• feat: Use api-utils for currency definitions (#5823)
• feat: Warn about non-unique names of functionsByType functions (#6001)
• feat(simple-pricing): Compute displayPrice as resolver as needed (#6025)

Fixes

• fix: a few 3.0 bugs (#5824)
• fix: account invite flow and account email data (#5799)
• fix: add missing permissions check to (#6040)
• fix: addAccountToGroup (#6071)
• fix: Adjust the sharp syntax (#5881)
• fix: canBackorder has lowercase o throughout codebase (#5990)
• fix: check if the url is already absolute (#6032)
• fix: comment out auth checks that aren't valid until new permissions are finished (#5900)
• fix: Don't use Packages for tax settings, and tax rates GQL fixes (#5852)
• fix: fix adding shop creator to owner group (#6072)
• fix: fix default public password reset URL (#5991)
• fix: Invisible Tags do not show on Admin tags list (#6028)
• fix: parse complicated MONGO_URL properly (#5827)
• fix: partialProductPublish for products without Catalog (#6059)
• fix: Polish translations (#6069)
• fix: problems with accounts queries (#6060)
• fix: Proper sitemap last modify date (#6078)
• fix: remove check for shopId where not needed (#5895)
• fix: respect allowGuestCheckout setting (#5815)
• fix: Return fulfillment quotes without a shipping address (#5934)
• fix: Some minor 3.0 fixes (#5977)
• fix: user roles and owner permission checks (#6008)
• fix: Various 3.0.0 fixes (#5722)
• fix: Various product GQL fixes (#6053)

Refactors

• refactor: add product media resolver & update translations for new DataTable products view (#6036)
• refactor: kieckhafer remove deprecations (#5718)
• refactor: add legacy system name to permission resource structure (#6019)
• refactor: cart token param name consistent to cartToken (#5820)
• refactor: clean up ENV/envalid code (#5922)
• refactor: clean up translations for products view (#5746)
• refactor: fix failing integration tests in release-3.0.0 (#5862)
• refactor: get roles / permissions directly from group(s), not user object (#6031)
• refactor: move xforms into plugins (#5713)
• refactor: No more Packages collection, implement AddressValidationRules GQL, other 3.0 stuff (#5888)
• refactor: only allow provides: default for one email address (#6062)
• refactor: pass cart down to calculateOrderTaxes fn (#6000)
• refactor: remove "owner" and other default permissions / groups (#6063)
• refactor: remove legacyRoles from authorization (#6021)
• refactor: Remove most remaining uses of users collection (#6056)
• refactor: remove restriction that limits account to one group per shop (#6035)
• refactor: rename simple-authorization to legacy-authorization, change function footprint (#5772)
• refactor: Replace context.queries.primaryShopId shopId with client shopId (#5802)
• refactor: source SMTP email configuation from ENV vars instead of DB (#5788)
• refactor: source Stripe API keys from ENV vars (#5771)
• refactor: use functionsOfType to register multiple auth permissions functions (#6009)
• refactor: use new URL instead of url.parse (#5717)

Chores

• chore: [3.0.0] Consolidate translation plugins (#5920)
• chore: add integration test for anonymousCartByCartId query (#5859)
• chore: add integration test for getFlatRateFulfillmentRestriction (#5869)
• chore: add integration test for getFlatRateFulfillmentRestrictions (#5866)
• chore: add integration test for globalSettings query (#5879)
• chore: add integration test for shopSettings query (#5873)
• chore: Check Node version (#5734)
• chore: copy over integration test from v2.x (#5854)
• chore: fix up eslintignore (#6026)
• chore: lock api-utils version number (#5851)
• chore: Node debugger config (#5993)
• chore: reconfigure docker-compose networks (#6068)
• chore: update Babel (#6065)
• chore: Upgrade mongodb and jest-mongodb (#5904)
• chore: use published image for docker-compose (#5992)

Docs

• docs: update links to use trunk branch of docs (#6050)

Tests

• test: add create/update/delete navigation item integration tests (#5890)
• test: add integration tes for recalculateReservedSimpleInventory mutation (#6010)
• test: add integration test available payment methods (#5864)
• test: add integration test for addressValidationServices query (#5930)
• test: add integration test for accountCartByAccountId query (#5857)
• test: add integration test for create, update & delete FlatRateFulfillmentMethod (#5964)
• test: add integration test for create, update & delete FlatRateFulfillmentRestriction mutations (#5981)
• test: add integration test for echo (#5942)
• test: add integration test for enablePaymentMethodForShop (#5944)
• test: add integration test for inviteShopMember mutation (#5984)
• test: add integration test for payment methods (#5883)
• test: add integration test for publishNavigationChanges mutation (#5969)
• test: add integration test for removeAccountAddressBookEntry (#5961)
• test: add integration test for removeAccountEmailRecord mutation (#5965)
• test: add integration test for setAccountProfileCurrency mutation (#5958)
• test: add integration test for setAccountProfileLanguage mutation (#5960)
• test: add integration test for taxCodes query (#5911)
• test: add integration test for updateAccountAddressBookEntry (#5962)
• test: Add integration tests for surcharge (#5938)
• test: add navigation query integration tests (#5856)
• test: add Tag query integration test (#5874)
• test: add updateTag mutation integration test (#5876)
• test: adds addressValidation query integration test (#5917)
• test: adds integration test for captureOrderPayments mutation (#6015)
• test: adds integration test for roles query (#5885)
• test: adds integration test for taxServices query (#5912)
• test: adds integration test for updateShopSettings mutation (#5974)
• test: adds integration test sitemap (#5889)
• test: adds integration test subrchargeById query (#5896)
• test: adds integration test surcharges (#5902)
• test: adds integration test updateGlobalSettings mutation (#5970)
• test: adds systemInformation query integration test (#5907)
• test: delete unused documents in afterAll (#5903)
• test: Eliminate factory mocks for catalogItemProduct (#5892)
• test: fix out-of-memory issues in tests (#5918)
• test: full cart/checkout integration test (#5976)
• test: integration test approve order payments mutation (#6013)
• test: integration test for update navigation tree (#5914)
• test: integration test set tag hero media (#6007)
• test: split query and mutation integration tests in CI config (#5919)
• test: Use Factory to mock FulfillmentMethod (#5988)
• test: Working integration tests (#5732)

Contributors

We couldn't have done this without the incredible people contributing to Reaction. From writing PRs and docs to creating bug reports, every contribution matters. Thanks to the over 60 people, involved in 8+ repos who have contributed in some way to the v3.0.0 release. We appreciate each of you! 🎉

@janus-reith @loan-laux @trojanh @HarisSpahijaPon

@adilsaeed31 @agustif @akakak1 @aktywnitu @albertstartup @alex-haproff @Arthur236 @ashwinsoni @Badyl1g @bjanssen-pon @BunnyMan1 @chriscamplin @cmbirk @CristianCucunuba @curmudgeonation @daniel-rosiak @deividaspetraitis @delagroove @DennisWanjiru @derBretti @desktp @dominik-myszkowski @Escalion @eusebiu-andrei9 @gddabe @hamxabaig @hems @ichtestemalwieder @ikabudimir @jackson-sandland @jdonor @jhonsfran1165 @jm18457 @jmav @joshreeves @juanzjck @karaarda @karbal @kmyn @manzettidenis @MarcMagnin @mauber91 @michaelstanton @moeghashim @monarkatfactly @Niko0918 @octoxan @okazdal @paales @preminfy @rogersoares @RoytenBerge @sagargupta @samkelleher @tccack @TilenKreca @vigyano @volanar @yashutanna @YuuwakU @Zachary-work

Notes

These changes were originally tested and released in our alpha and beta releases

• v3.0.0-beta.3
• v3.0.0-beta.2
• v3.0.0-beta
• v3.0.0-alpha.3
• v3.0.0-alpha.2
• v3.0.0-alpha

The following Reaction projects are being released one time in coordination as v3.0.0

• Reaction API
• Reaction Hydra
• Reaction Identity
• Reaction Admin (beta)
• Example Storefront
• Reaction Development Platform

After this release, Reaction releases will no longer be coordinated across all projects - we'll release each project independently, as needed. Version numbers will no longer be kept in sync. The newest versions of each project will work together.

v2.9.0

Reaction v2.9.0 adds integration tests for GraphQL API endpoints, security updates and fixes a fulfillment method bug.

This release is being coordinated with Reaction Platform and is designed to work with v2.9.0 of Reaction Hydra and Example Storefront.

Notable changes

Add integration tests and increase maxWorkers

As a part of the major push to remove the Meteor dependency from the GraphQL API, we've been adding more Jest integration tests with the goal of full integration test coverage for all GraphQL queries and mutations provided by all core and included plugins. In this release, we've added tests for the following GraphQL queries: shopBySlug, orderByReferenceId, ordersByAccountId, addTag and removeTag. See test coverage epic here.

Fix a fulfillment bug

Refactors the updateOrderFulfillmentGroup GraphQL mutation to update only the specified group, not all fulfillment groups.

Update packages for security vulnerabilities

Bumps @reactioncommerce/data-factory to version 1.0.1 and @reactioncommerce/job-queue to version 1.0.5.

Tests

• Add integration tests for shopBySlug GraphQL query #5701
• Add integration tests for orderByReferenceId GraphQL query #5697
• Add integration tests for ordersByAccountId GraphQL query #5696
• Add integration tests for addTag GraphQL query #5683
• Add integration tests for removeTag GraphQL query #5687

Security

• Upgrade insecure package versions #5745

Refactors & Fixes

• Only update fulfillment group for which id is provided #5723

Contributors

Thanks to @YuuwakU for contributing to this release! 🎉

v2.8.1

Reaction v2.8.1 adds a bug fix and contains no breaking changes since v2.8.0

This release is being coordinated with reaction-platform and is designed to work with v2.8.1 of example-storefront and reaction-hydra.

Notable changes

Fix password reset issue

Password reset has been fixed to correctly send a password reset email, and re-direct the user once their new password has been set.

Fixes

fix: password-reset route not working correctly (#5744)

v2.8.0

Reaction v2.8.0 adds performance enhancements and fixes bugs.

This release is being coordinated with Reaction Platform and is designed to work with v2.8.0 of Reaction Hydra and Example Storefront.

Notable changes

Fix memory issues in jest tests

Jest integration tests were failing due to a memory leak in async test code. We have closed that memory leak with this release.

Fixes

Merge pull request #5733 from reactioncommerce/fix-aldeed-memory-issues

• fix: fix memory issues with jest tests (#5733)

v2.7.0

Reaction v2.7.0 adds performance enhancements and fixes bugs.

This release is being coordinated with Reaction Platform and is designed to work with v2.7.0 of Reaction Hydra and Example Storefront.

Notable changes

More packages have continued to migrate from no-meteor folders to node-app

As part of de-meteorization of the Reaction API, We have continued the migration of moving all server side code in no-meteor folders to their respective node-app folders.

Potential Breaking Changes for Custom Plugins

There might be breaking changes in custom plugins due to the movement of core packages to the node-app folders. Custom plugins will need to update their imports paths to reflect the new location of packages.

Fixes

• fix: pass correct userId when creating a shop (#5694)
• fix: filter products by file on Windows (#5700)

Refactors

• refactor: Move accounts plugin to Node app and better split accounts from users/IDP (#5693)
• refactor: clean-up tasks related to removing appEvents from all meteor code (#5692)
• refactor: clean-up tasks related to moving files to the node-app (#5688)
• refactor: simpleSchema updates for mockContext (#5685)
• refactor: move getPaymentMethodConfigByName to context (#5684)
• refactor: create archiveProducts GQL mutation to replace meteor methods (#5680)
• refactor: move jobs-queue from server/no-meteor to node-app (#5678)
• refactor: move cart from server/no-meteor to node-app (#5675)
• refactor: move checkout from server/no-meteor to node-app (#5674)
• refactor: move core plugin to Node app (#5673)
• refactor: move discounts plugins to Node app (#5672)
• refactor: move marketplace to Node app (#5671)
• refactor: move orders from server/no-meteor to node-app (#5670)
• refactor: move catalog from server/no-meteor to node-app (#5658)
• refactor: move navigation from server/no-meteor to node-app (#5656)
• refactor: move email from server/no-meteor to node-app (#5655)
• refactor: move i18n from server/no-meteor to node-app (#5654)
• refactor: move product and product-variant from server/no-meteor to node-app (#5669)
• refactor: move sitemap-generator from server/no-meteor to node-app (#5667)
• refactor: move Tags from server/no-meteor to node-app (#5665)
• refactor: move dashboard from server/no-meteor to node-app (#5663)
• refactor: move product-admin plugin to Node app (#5659)
• refactor: move notifications plugin to Node app (#5661)

v2.6.0

Reaction v2.6.0 adds minor features and performance enhancements, fixes bugs and contains no breaking changes since v2.6.0.

This release is being coordinated with Reaction Platform and is designed to work with v2.6.0 of Reaction Hydra and Example Storefront.

Notable changes

Packages have begun to migrate from no-meteor folders to node-app

As part of de-meteorization of the Reaction API, We have started the migration of moving all server side code in no-meteor folders to their respective node-app folders.

Feature

• feat: add product and productVariant related GraphQL mutations (#5562)

Fixes

• fix: product medatafield UI issues (#5584)

Refactors

• refactor: move email-smtp from server/no-meteor to node-app (#5641)
• refactor: move ui from server/no-meteor to node-app (#5637)
• refactor: move address-validation-test from server/no-meteor to node-app (#5638)
• refactor: move shipping and surcharges from server/no-meteor to node-app (#5632)
• refactor: move settings from server/no-meteor to node-app (#5634)
• refactor: ackground jobs rewrite: no Meteor dependencies! (#5580)
• refactor: move address from server/no-meteor to node-app (#5587)
• refactor: move template from server/no-meteor to node-app (#5586)
• refactor: use reaction-error external package instead of internal alias (#5631)
• refactor: move system-information from server/no-meteor to node-app (#5585)
• refactor: rewrite removeAccountEmail without meteor (#5577)

v2.5.0

Reaction v2.5.0 adds minor features and performance enhancements, fixes bugs and contains no breaking changes since v2.4.0.

This release is being coordinated with Reaction Platform and is designed to work with v2.5.0 of Reaction Hydra and Example Storefront.

Notable changes

Filters have been added to Orders query

Adds API support to enable users to filter orders by: search keywords (fuzzy search), status, payment status, fulfillment status, date range.

Faster Jest integration tests

By switching to jest-mongodb, we've seen 8x speed improvement when running npm run test:integration

Feature

• feat: add various filters to the main orders query (#5575)
• feat: Translations without Meteor (#5514)

Fixes

• fix: restore Add/Remove menu item in products page (#5564)
• fix: use catalyst button for mediauploader (#5563)
• fix: restore loadTranslations fn (#5546)
• fix: Add missing GraphQL argument descriptions (#5547)

Refactors

• refactor: create verifySMTPEmailSettings GraphQL mutation, replace meteor version (#5531)
• refactor: various small fixes (#5561)
• refactor: Add extra field to the error message (#5574)
• refactor: use CardHeader for Filter by File card (#5569)
• refactor: add indices on updatedAt for CDC (Products & SimpleInventory) (#5571)
• refactor: rewrite accounts/sendResetPasswordEmail into a GraphQL mutation (#5558)
• refactor: remove Reaction.Email (#5559)
• refactor: remove all code releated to inviting a shop owner (#5553)
• refactor: Fix proptype warning with ReactSortableTree (#5552)
• refactor: remove catalog/publish/products meteor method, use publishProductsToCatalog GQL Mutation instead (#5541

Tests

• tests: faster Jest integration tests (#5549)

Docs

• docs: Fix test command in README.md (#5565)

Chores

• chore: fix various prop type validation errors (#5550)

v2.4.0

Reaction v2.4.0 adds minor features and performance enhancements, fixes bugs and contains no breaking changes since v2.3.0.

This release is being coordinated with Reaction Platform and is designed to work with v2.4.0 of Reaction Hydra and Example Storefront.

Notable changes

Translations have been moved out of Meteor

i18n translations have been moved outside of the Meteor context. This provides a standard route, /locales/resources.json, where all translations live, and allows for real-time updates to translations without needing to flush the cache.

Meteor app-tests have

As part of our move away from Meteor, all Meteor app-tests have been removed. This speeds up both local testing, and testing on CI.

Feature

• feat: Translations without Meteor (#5514)

Fixes

• fix: restore Add/Remove menu item in products page (#5564)
• fix: use catalyst button for mediauploader (#5563)
• fix: restore loadTranslations fn (#5546)

Refactors

• refactor: remove Reaction.Email (#5559)
• refactor: remove all code releated to inviting a shop owner (#5553)
• refactor: Fix proptype warning with ReactSortableTree (#5552)
• refactor: remove catalog/publish/products meteor method, use publi#5541hProductsToCatalog GQL Mutation instead (#)

Tests

• tests: Faster Jest integration tests (#5549)

Docs

• docs: Fix test command in README.md (#5565)
• docs: Add missing GraphQL argument descriptions (#5547)

Chores

• chore: remove meteor app-tests (#5560)
• chore: fix various prop type validation errors (#5550)

v2.3.0

Reaction v2.3.0 adds minor features and performance enhancements, fixes bugs and contains no breaking changes since v2.2.1.

This release is being coordinated with reaction-platform and is designed to work with v2.3.0 of example-storefront and reaction-hydra.

Notable changes

Bulk add and remove Tags from Products

Reaction Admin users can now add and remove tags from products in bulk. After selecting multiple products in the product table or filtering products with a CSV file, users can specify tags they'd like to add or remove from those products.

This feature uses several new components from the Catalyst Design System, including SplitButton, Chip and MultiSelect. Several dependencies, including react-select, react-dropzone and material-ui/core were upgraded to their latest versions.

Image uploading without Meteor

file-collections has been updated to its latest version, which supports uploading without Meteor. All related code has been updated to remove Meteor.

Remove context.callMeteorMethod

All GraphQL mutations which still used Meteor methods via the context.callMeteorMethod function - inviteShopMember, addressBookRemove, removeAccountFromGroup, setAccountProfileCurrency, updateAccountAddressBookEntry - have been updated to fully use GraphQL. In turn context.callMeteorMethod is no longer used, and has been removed from the codebase.

Feature

• feat: manage product tags in bulk (#5485)
• feat: Add Orders GraphQL query (#5483)
• feat: Image uploading without Meteor (#5515)

Fixes

• fix: info inline alert should autoclose (#5502)
• fix: Perform old password validation (#5527)

Refactors

• refactor: use moments calendar format to display time alongside date (#5523)
• refactor: remove context.callMeteorMethod (#5524)
• refactor: remove inviteShopMember meteor method and rewrite with GraphQL (#5520)
• refactor: remove addressBookRemove meteor method and rewrite with GraphQL (#5492)
• refactor: remove removeAccountFromGroup meteor method and rewrite with GraphQL (#5493)
• refactor: add setAccountProfileCurrency GraphQL mutation (#5488)
• refactor: rewrite updateAccountAddressBookEntry to not call through to Meteor method (#5484)

Tests

• tests: Add Integration Test for orderById GraphQL query (#5511)

Contributors

Thanks to @trojanh for contributing to this release! 🎉

v2.2.1

Reaction v2.2.1 adds a bug fix and contains no breaking changes since v2.2.0

This release is being coordinated with reaction-platform and is designed to work with v2.2.1 of example-storefront and reaction-hydra.

Fixes

• fix: Checkout hangs on shipping methods step (#5516) and adds a migration to avoid breaking previous installations. The issue was caused by attempting to add a fulfillment method to a cart that included the prop fulfillmentTypes, which was not part of the ShippingMethod schema, which caused a validation error. This issue was resolved by adding the fulfillmentTypes prop to the ShippingMethod schema.

Contributors

Thanks to @alex-haproff for contributing to this release! 🎉

v2.2.0

Reaction v2.2.0 adds minor features and performance enhancements, fixes bugs and contains no breaking changes since v2.1.0.

This release is being coordinated with reaction-platform and is designed to work with v2.2.0 of example-storefront and reaction-hydra.

Notable changes

Elimination of all eslint warnings

The Reaction code base is now clean of all eslint warnings. Going forward, all eslint rules have been changed to error, and CI will fail if any are present.

Product filtering by CSV

Admins can filter products by uploading a CSV in the product admin.

Introduce Apollo hooks

Apollo has been updated to v3.0.0, which introduces GraphQL hooks into Reaction.

Updated Orders Admin UI

The new Orders UI allows is completely GraphQL based and allows for updates to multiple fulfillment groups on each order.

Remove Snyk as a CI step

Snyk was unable to work with PR's from forked repositories, which in turn caused every contribution to fail the CI check. We have removed Snyk as a blocking CI check because of this, and will run it locally on a schedule to still see which packages are in need of an update.

Feature

• feat: add offset for pagination with tests (#5228)
• feat: bulk actions UI updates (#5461)
• feat: add refunds GraphQL query (#5352)
• feat: #5366 show filter count (#5395)
• feat: #5379 integrate catalyst button (#5406)
• feat: add bulk mutations to manage products and tags (#5404)
• feat: remove startup template import (#5430)
• feat: add new setting to allow / disallow custom user locale lookup (#5444)
• feat: add isvisible/hidden icons (#5407)
• feat: Part I: An admin user can filter products by uploaded CSV (#5451)

Fixes

• fix: style the product table as close as possible (#5468)
• fix: console warnings (#5463)
• fix: update comp-lib to fix broken components (#5475)
• fix: add check against missing riskLevel field, and missing string in capitalization function (#5452)
• fix: partial product publish error (#5433)
• fix: popover z-index (#5437)
• fix: issues with refund queries (#5422)
• fix: load account into context during surcharges (#5466)
• fix: Correct index migration (#5408)

Chores

• chore: add redirect for blank route (#5439)
• chore: update vulnerable packages (#5470)
• chore: update reaction to use reaction-eslint-rules v2.1.0 (#5445)
• chore: remove unused shop.appVersion (#5429)
• chore: update bodyParser to use individual method (#5435)
• chore: use file extensions for node 12 compatibility (#5415)
• chore: remove snyk as a CI task (#5403)
• chore: Update Apollo packages to support hooks (#5427)
• chore: update catalyst sidebar font and color styles (#5494)

Refactors

• refactor: use SplitButton from Catalyst instead of ConrifmButton (#5469)
• refactor: Rewrite addAccountToGroup to not call through to Meteor method (#5431)
• refactor: after-publish cart updates for speed (#5477)
• refactor: order invoice print layout (#5476)
• refactor: update Reaction Admin Orders panel (#5158)
• refactor: payments-stripe to only use getStripeInstanceForShop (#4951)
• refactor: add tag permissions to allow non-owner to edit (#5436)
• refactor: refunds section of Orders 2.0 (#5405)
• refactor: move filter outside of admin check (#5434)
• refactor: use Accounts collection instead of Meteor.users to get admin accounts (#5432)
• refactor: Remove legacy social plugin, PDP, product grid and WYSIWYG code (#5394)
• refactor: expanded product admin permissions (#5428)

Style

• style: update jsdoc to always use returns instead of return (#5447)
• style: ESLint errors and warnings === 0 (#5450)

Tests

• test: add integration test for primaryShop query (#5459)

Breaking Changes

None

Contributors

Thanks to @cmbirk, @loan-laux and @rattrayalex-stripe for contributing to this release! 🎉

v2.1.0

Reaction v2.1.0 adds minor features and performance enhancements, fixes bugs and contains no breaking changes since v2.0.0.

This release is being coordinated with reaction-platform and is designed to work with v2.1.0 of example-storefront and reaction-hydra.

Notable changes

Introduction of Catalyst

Our new Catalyst design system has been introduced into the Reaction codebase, and is used on various components including ConfirmDialog and Button. All new default component theme modifications must come from Catalyst.

Tag slugs are now editable independently of tag name

Allows operators to change aa tag slug independently of a tag name.

Order related GraphQL mutations

A createRefund GraphQL mutation has been added to allow refunds to be processed via GraphQL in addition to the existing meteor methods.

Dataloaders introduced into the codebase

"DataLoader is a generic utility to be used as part of your application's data fetching layer to provide a simplified and consistent API over various remote data sources such as databases or web services via batching and caching."

Added the first couple of DataLoaders for Shops and SimpleInventory. Shops will benefit product listing pages as product and variant resolvers all query Shops collection for each product. SimpleInventory query benefits from batching.

Bulk simple inventory mutation

When running large inventory import via an external sync system, the lack of a bulk mutation made the import takes many hours. This update introduces a bulk import option which cuts down import time significantly.

Overhaul of eslint rules, and bulk fix of over 500 eslint warnings

We've updated to using v2.0.0 of our Reaction ESLint Config package, and have brought our eslint warnings down from 800 to under 300.

Feature

• feat: catalog partial publish / rerun transformations (#5355)
• feat(product table): show Action dropdown, even if no products are selected (#5391)
• feat: filter products by id in products table (#5387)
• feat: editable tag slug (#5382)
• feat: add createRefund GraphQL mutation (#5354)
• feat: add handle to tag autosuggest results (#5262)
• feat: Add DataLoaders for Shops and SimpleInventory (#5294)
• feat: Introduce DataLoaders infrastructure (#5280)
• feat: new button component to wrap MUI button with isWaiting loading state (#5266)
• feat: bulk simple inventory mutation (#5229)
• feat: integrate catalyst ConfirmDialog component from new Catalyst package (#5372)

Fixes

• fix: set slugified title as permalink (#5264)
• fix: Add migration for index (#5358)
• fix: red textfields (#5371)
• fix: Make catalog indexes unique for product (#5350)
• fix: fix consistent-return eslint warnings (#5334)
• fix: replace simpl-schema.validate() … (#5306)
• fix: use SimpleInventory collection to fe… (#5314)
• fix: #5300 Wrong template reference (#5301)
• fix: typo breaking docs build (5286) (#5287)

Performance Improvements

• perf: wrap tests in check to make sure app is ready when they run (#5317)
• perf: up data transfer limit to allow bigger sizes (#5396)

Docs

• docs(admin): Introducing Reaction Admin (#5400)
• docs(readme): introducing the Storefront Component Library to develop (#5398)
• docs: Update README.md (#5319)

Chores

• chore: updated Dockerfile to change .meteor/ permissions to the node … (#5353)
• chore(ci): add eslint check to only check changed files and fail when warnings are thrown (#5357)
• chore(ci): Work more robustly on forks (#5386)
• chore: fix no-undef lint issues (#5360)
• chore: update Material-UI 4.x (#5278)
• chore: Update README DCO - sign-off not sign (#5318)
• chore: update snyk ignore (#5331)
• chore: update CHANGELOG, update version (#5260)
• chore: use npm command rather than meteor npm (#5328)
• chore: update js-doc throughout the app, batch 1 (#5309)
• chore: fix all react/no-deprecated and react/prop-type eslint warnings (#5307)
• chore: update reaction-eslint-config version in package.json (#5320)
• chore: organize integration tests (#5316)
• chore: add overrides for eslint rules that stlll need fixing (#5308)
• chore: fix all id-length eslint warnings (#5298)
• chore: update lodash to fix snyk critical error (#5299)
• chore: fix all max-len eslint warnings (#5296)
• chore: fix prefer-const eslint error (#5290)

Refactors

• refactor: add title as backup in product admin breadcrumb (#5342)
• refactor: add isSoldOut prop to variants and options in Catalog (#5289)
• refactor: how to get reaction version (#5324)
• refactor: fulfillment section of Orders 2.0 (#5302)
• refactor: payments section of Orders 2.0 (#5279)

Tests

• test: add integration test for ping query (#5326)

Breaking Changes

None

Contributors

Thanks to @janus-reith for contributing to this release! 🎉

v2.0.0

Reaction v2.0.0—an API-first, real-time commerce engine built using Node.js, React, and GraphQL. It’s the second major release of our open source commerce software.

This release is coordinated with Reaction Platform and is designed to work with the Example Storefront (previously Storefront Starter Kit) and [reaction-hydra](https://github.com/reactioncommerce/reaction-hydra).

Reaction v2.0.0 is built as a truly headless commerce platform that decouples the Reaction backend services from the frontend. We’ve decoupled the storefront application from the API. Reaction platform now consists of the reaction project, which is now primarily our GraphQL API, and for the time being also our operator UI and our identity provider, along with our new to 2.0 Example Storefront, built on Next.js, which connects with the Reaction application via GraphQL API to provide a customer-facing storefront. The legacy integrated Meteor storefront is no longer part of the Reaction project.

Notable changes

Check out previous release notes for details and associated issues and PRs.

Operator experience and UI The store operator experience has been substantially enhanced from v1.x. We’ve shifted the operator UI for managing products from a What You See Is What You Get (WYSIWYG) product editor to one that is designed for greater flexibility. We have transitioned from a single-page admin experience to a full-page operator experience that’s fully separate from the storefront. The new operator UI uses 100% of the screen space for store management and operation, and will benefit users managing large product catalogs and complex fulfillment patterns.

We’ve also added lots of new functionality around tags (tag dashboard and new tag management features), site navigation (including sitemaps and navigation tree editor), and fulfillment options (ability to add restrictions or surcharges based on product tags and/or customer location).

GraphQL API coverage Most Meteor methods are removed in favor of the new GraphQL API. GraphQL is the only way to interact with the API from a storefront app. The operator UI uses a mixture of GraphQL and Meteor DDP while we complete the transition to GraphQL on the administrative side.

Developer experience and performance For developers, we’ve made a number of enhancements to improve the overall developer experience, especially debugging, logging, and updated documentation.

• Examples for how to debug Node.js in Docker
• Better logging of packages and plugins loading
• bin/setup improvements
• Updated main Reaction app to use .env file (#4826)
• Added envalid for validation of environment variables

We’ve made some tweaks to increase performance and improve initial boot time:

• Removed reaction-cli (v2.0.0-rc.10)
• Added and removed a number of indexes since 1.x, see #4819, #5106, #5090, etc. for examples

We’ve also improved Reaction’s extensibility in a number of ways, such as:

• Reaction now supports remote graphql schemas in plugins (#4870)
• Plugins can now directly register React components (#4875)
• Plugins can register functions to handle GraphQL transformation of catalog product media items (#4988)
• There is now a collections option for registerPlugin, which allows plugins to define their MongoDB collections and indexes in a standard way (#5196)

And finally, we’ve updated all Reaction dependencies (such as React and Apollo) to the latest versions, and updated our base docker image to use Meteor 1.8 (#4760).

Security audit For the 2.0 release we’ve done a full security audit of the application, including cart, order methods, payment processing methods, and more, and fixed potential vulnerabilities.

Other updates

• Authentication is now handled via Hydra
• Taxes have been completely re-worked in a new plugin (v2.0.0-rc.10)
• Inventory has been moved into its own simple-inventory plugin, and is no longer directly tied to the Products collection
• Pricing has been moved into its own simple-pricing plugin, and allows for a 3rd party pricing service integration. (#5014 & #5143)
• Search plugins have been removed (#5053)
• A plugin can now be used to override the default orderId and cartId and create IDs of a different type or in a specific order (#5054)

New documentation

See this page for a non-comprehensive list of new and updated docs.

Some highlights:

• A Storefront UI Development guide answering "How do I build a storefront for Reaction or adapt my storefront to get its data from Reaction, without starting from an example app"
• Helpful info about GraphQL Resolvers and extending GraphQL to add a field
• A guide for “How To Extend the Product Schema”

OS notes

Support for Windows. [reaction-platform](https://github.com/reactioncommerce/reaction-platform) is not compatible with Windows and has not been fully tested on Windows at this time.

MacOS and Linux are supported. Reaction will support development in a dockerized environment and will focus on tooling and documentation for installation and configuration on the macOS and Linux OSes.

We've adopted the DCO

We've adopted the Developer Certificate of Origin (DCO) in lieu of a Contributor License Agreement for all contributions to Reaction Commerce open source projects. We request that contributors agree to the terms of the DCO and indicate that agreement by signing all commits made to Reaction Commerce projects by adding a line with your name and email address to every Git commit message contributed:

Signed-off-by: Jane Doe <[email protected]>

You can sign your commit automatically with Git by using git commit -s if you have your user.name and user.email set as part of your Git configuration.

We ask that you use your real name (please no anonymous contributions or pseudonyms). By signing your commit you are certifying that you have the right have the right to submit it under the open source license used by that particular Reaction Commerce project. You must use your real name (no pseudonyms or anonymous contributions are allowed.)

We use the Probot DCO GitHub app to check for DCO signoffs of every commit. If you forget to sign your commits, the DCO bot will remind you and give you detailed instructions for how to amend your commits to add a signature.

We're following in the footsteps of several other open source projects in adopting the DCO such as Chef, Docker, and GitLab

Contributors

Our sincere thanks to @rattrayalex-stripe, @willmoss1000, @pmn4, @loan-laux, @lcampanis and the @artlimes folks, and everyone on our Community Council for contributing to this release.

Share your feedback

We want to hear from you! Here are some good ways to get in touch.

• Want to request a new feature for Reaction? There’s now a Reaction repo just for new feature requests.
• Reaction engineers and community engineers and developers are always collaborating in our Gitter chat channel
• Ask Us Anything! Watch this space for details about an upcoming Community Q&A session with the Reaction team.

v2.0.0-rc.12

This is our twelfth release candidate for v2.0.0 of Reaction. Please check it out and let us know what works and what doesn't for you.

This release is being coordinated with reaction-platform and is designed to work with the same versions of example-storefront and reaction-hydra.

Improvements

Feature

• feat: better cart and order item attributes, with labels (#5253)
• feat: add shopLogoUrls to shop settings to allow logo to be rendered from url (#5227)
• feat: add resolver to get displayStatus from database (#5236)
• feat: Add DetailDrawer component for supplementary views (#5239)
• feat: add regex filter to tags GQL query (#5232)
• feat: add landing page for catalyst (#5226)
• feat: update sidebar, fix mobile responsiveness (#5209)
• feat: hard code cache keys prefix (#5222)
• feat: add read-only version of orders 2.0 to break up PR’s (#5202)
• feat: add approveOrderPayments graphql mutation (#5201)
• feat: dangerButton and ConfirmButton components (#5200)
• feat: define collections using registerPlugin (#5196)
• feat: update default navigation item visibility options when added to the navigation tree (#5190)
• feat: storefront login url (#5187)
• feat: add a setting for whether options without inventory enabled are sellable (#5186)
• feat: UI for adding Storefront Urls inside Catalyst (#5174)
• feat: additional navigation visibility options (#5153)
• feat: add ENV to disable inventory auto-publish (#5149)
• feat: migrations & related checks can be disabled (#5140)
• feat: allow 10 levels of navigation tree (#5129)
• feat: add Catalog query filters (#5126)
• feat: ShopId can be any string (#5119)
• feat: use shop logo for login pages (#5109)
• feat: drop unnecessary MongoDB indexes (#5106)
• feat: adds optional flag to filter out sold-out products (#5105)
• feat: allow viewing of orders by reference id (#5092)
• feat: plugin: Prometheus Metrics (#5088)
• feat: feature/system info (#5087)
• feat: add name related data to viewer Account query (#5079)
• feat: replace reaction plugins usage (#5070)
• feat: Add cart referenceId in graphql schema (#5065)
• feat: registerBlock API for registering blocks and rendering components for regions (#5064)
• feat: allow extend generate orderId and cartId (#5054)
• feat: de-Meteorize emailing code in the API (#4998)

Fix

• fix: socket issues (#5255)
• fix: Make new order email links correct for storefront (#5251)
• fix: ensure translations from all packages load (#5252)
• fix: Fix page title from not found (#5245)
• fix: alphabetical currencies (#5230)
• fix: app will not start (#5216)
• fix: shop with data error (#5207)
• fix: change calibre ci step to use npx (#5197)
• fix: NaN for prices with commas (#5193)
• fix: add subtotal display amount to dataForOrderEmail (#5183)
• fix: remove product-admin dead import (#5180)
• fix: Can't re-send shop manager invite to existing non-activated user (#5178)
• fix: set shop manager password on invitation (#5173)
• fix: replaceBlock function (#5161)
• fix: detect and add a newline in .env file if its missing (#5156)
• fix: race condition by awaiting each publish catalog function by type… (#5151)
• fix: inventory quantity resets to 0 when any variant or option quantity is undefined (#5134)
• fix: remove transform for billingAddress in gql resolver for Payment (#5125)
• fix: add correct item images to order email data (#5121)
• fix: password reset form (#5120)
• fix: include submodule bare repos in docker build context (#5118)
• fix: extendCommonOrder items data was over-written by itself (#5104)
• fix: orders performance (#5096)
• fix: revert metrics prometheus (#5099)
• fix: catalog items performance (#5095)
• fix: rounding Issue in Cart/Orders (#5091)
• fix: remove aldeed:schema-index Meteor package, use collectionIndex (#5090)
• fix: make tax code field available for new rate (#5076)
• fix: duped cart referenceId (#5074)
• fix: shipping restrictions not correctly denying methods (#5071)
• fix: navigation editor WSOD when navigation tree is empty (#5067)
• fix: set variant media correctly when added to cart (#5063)
• fix: marketplace invitation validation (#5057)

Chore

• chore: Remove unused npm deps and update to latest Babel (#5250)
• chore: update @reactioncommerce/file-collections version (#5244)
• chore: Omit email credentials from log data (#5241)
• chore: update styles for MUI Typography to match designs (#5235)
• chore: Move some core files to new shop plugin (#5233)
• chore: Update NPM packages (#5231)
• chore: Update React 16.8.6 (#5204)
• chore: add language to shop query (#5203)
• chore: remove Profile (#5198)
• chore: finish simple-pricing plugin (#5143)
• chore: add a GraphQL schema linter, fix found issues (#5112)
• chore: ignore js-yaml vuln for 30 days (#5108)
• chore: security update for js-yaml (#5093)
• chore: ensure an error message is logged for apollo errors (#5061)
• chore: more consistent Usage of ES6+ Code (#5056)

Refactors

• refactor: Demeteorize registration for remaining API server plugins (#5234)
• refactor: Rename graphql endpoint (#5249)
• refactor: update styling of orderCard header section, move details to sidebar (#5240)
• refactor: enhancements to tag ui in Catalyst (#5223)
• refactor: inventory Rewrite - new simple-inventory plugin (#5164)
• refactor: add home, order, orders, and account profile urls to shop object (#5145)
• refactor: use getVariantPrice to determine price in xformCartGroupToCommonOrder (#5142)
• refactor: add env. vars. for graphql playground and introspection (#5055)

Performance

• perf: minor inventory performance improvments (#5220)
• perf: demeteorize and reorg some core startup code (#5212)
• perf: avoid unnecessary database queries for common GraphQL requests (#5154)
• perf: faster inventory updates (#5138)
• perf: create index for Jobs queries (#5137)
• perf: improved performance for products and catalog items queries with featured sort (#5136)
• perf: tag subscription (#5130)
• perf: speed up the products table publication (#5128)
• perf: remove unused Meteor methods and client cart code (#5059)

Breaking Changes

• uiState.isLeftSidebarOpen renamed to uiState.isPrimarySidebarOpen (#5209)
• Breaking workflow, every item added to the nav tree will need to be explicitly made visible on the storefront (#5190)
• There is a new shop-specific app setting, canSellVariantWithoutInventory, which is true by default. If this is changed to false, then variants/options without inventory tracking enabled will appear sold out and with back-ordering disabled. (#5186)
• navigationTreeById now accepts an object containing params { language, navigationTreeId, shouldInlcudeSecondary } instead of individual params. (#5153)
• draftItems is admin only now so to not expose work-in-progress changes to the public
• Potential for http routing conflicts on /metrics. (#5088)
• Product components have been broken into smaller peices and the old files removed. This should be an internal breaking change as prior to this PR, those components couldn't be modified without touching core. (#5064)
• The new order confirmation email template has been updated (#5251)
• Multi-shop orders will no longer work (#5096)
• If you have custom plugins that use index or unique options in their schemas, add back the aldeed:schema-index dependency or update the plugins to use collectionIndex function. (#5090)
• Custom plugins importing any of the removed packages or using the removed component will need to be updated. (#5250)
• The deprecated price field has been removed from CatalogProduct and CatalogProductVariant. (#5143)
• Custom plugins that manage or use inventory are likely to need a rewrite. (#5164)
• Older shops must confirm they are using our simple-pricing plugin, and that pricing is available on Catalog items. (#5142)
• Removed support for undocumented feature Meteor.settings.cdnPrefix
• Removed support for undocumented feature Reaction.Endpoints
• Removed support for prerender by prerender-node NPM package (#5212)
• Tags are no longer subscribed to at a global level. Subscribe to tags when you need them using Meteor.subscribe("Tags", [tagIds]); (#5130)
• Any custom plugins relying on the removed Meteor methods will need to be updated. (#5059)

v2.0.0-rc.11

This is our eleventh release candidate for v2.0.0 of Reaction. Please check it out and let us know what works and what doesn't for you.

This release is being coordinated with reaction-platform and is designed to work with the same versions of reaction-next-starterkit and reaction-hydra.

Improvements

App

Reaction is no-longer a customer-facing app, it's an administration tool and offers a GraphQL API.

All customer-facing views are the responsibility of a separate storefront app that makes use of the GaphQL API. See our example storefront as an example of how to achieve this.

• All routes require admin authentication
• All non-admin authentication requests will be met with a logout screen if attempting to sign into the operator experience.
• All customer related authentication requests should be done with the IDP workflow. See our example storefront as an example of how to achieve this.

Product grid and Product detail pages moved into the new operator experience and updated for that experience.

Product grid

Product grid is now represented as a table in the new experience with the same bulk actions it had previously

• Product grid is now a table
• Product table supports multi-selection
• Product table supported bulk actions are "Make Hidden", "Make Visible", Archive, Duplicate and Publish
• Product table adds simple pagination controls with and items per page selector

Product Detail Page

Is no longer a WYSIWYG editor.

All product forms have been moved on from the sidebar and into the main view and have been expanded.

• Product WYSIWYG editor has been replaced with standard forms
  • Product detail, Variant and Option forms have been moved out of the sidebar and into the primary view
• Template field has been converted to text field from a dropdown. Templates no longer apply to the PDP page in Reaction
• Tags can no longer be drag n' dropped to reorder. Drag handle has been removed to represent this.
• Media can be added to the Product, Variants, and Options
• Drag n' Drop of media and variants has been removed
  • Variants and Options can now be manually sorted by priority
  • Media can be sorted by priority manually
• Variant and Options forms now share the same fields

User Profile

• The profile page has been moved to the new operator experience for admins
• Address form has been removed
• Order history has been removed
• Admins will be able to change their email and password

Breaking Changes

Reaction is no-longer a customer-facing app, it's an administration tool and offers a GraphQL API.

We have removed the search-mongo and ui-search plugins from the imports/plugins/included directory of reaction. Which in turn removes order search bar from operator order UI. (#5053)

Feature

• feat: remove search plugins (#5053)
• feat: allow users to disable plugins via config (#5031)
• feat: add addOrderFulfillmentGroup mutation (#5027)
• feat: add splitOrderItem mutation (#5024)
• feat: add updateOrderFulfillmentGroup mutation (#5020)
• feat: add updateOrder mutation (#5019)
• feat: add moveOrderItems mutation (#5018)
• feat: add cancelOrderItem mutation (#5010)
• feat: Operator 2.0 products admin (#5005)
• feat: performance metrics integration with calibre (#5012)
• feat: simple-pricing plugin (#5014)
• feat: use .env.example files from custom plugins (#5003)

Fix

• fix: bin/setup handling bad env.example (#5048)
• fix: naming issue caused taxes to not be calculated (#5043)
• fix: startup asset provisioning (#5033)
• fix: make bin/setup more robust to missing directories (#5026)
• fix: item subtotal is incorrect when additional quantities of the same item are added to cart (#5021)

Chore

• chore: add better logging of package loading (#5051)
• chore: add optional first and last name fields to schemas (#5050)

v2.0.0-rc.10

This is our tenth release candidate for v2.0.0 of Reaction. Please check it out and let us know what works and what doesn't for you.

This release is being coordinated with reaction-platform and is designed to work with the same versions of reaction-next-starterkit and reaction-hydra.

Improvements

UI Removal

We have removed several UI components to transition and solidify that in 2.0 the application will only be used as an API and a UI for shop operators.

Additional PRs will be coming to remove other pieces of the storefront UI bit by bit until only an operator UI is left. (#4947 , #4948)

Performance Tweaks

• We have done a bunch of performance tweaks to increase performance and initial boot time! We removed the reaction-cli with this update. (#4992)

General

• We have added the ability for shops to apply surcharges depending on criteria for an order. (#4829)
• We have added a new Navigation Manager UI for Operator 2.0. (#4936)
• We have added envalid as a dependency for validating environment variables. (#4983)

GraphQL

• We have streamlined the way plugins register functions that can transform media objects for a product. (#4987)
• We have implemented GraphQL subscriptions support. (#4938)

Custom Data

• We have added the capability to add a custom data object when placing an order. (#4962)
• We have added the capability for calculateOrderTaxes to return a custom data object. (#4955)

Custom Plugins

• We have coalesced the separate env.example files from custom Reaction plugins into one file to reduce tedious integration steps. (#5003)

Breaking Changes

AppEvents

• We have replaced all Hooks usage with the newer appEvents. This does not break anything within the core and included plugins, however: If you use community or custom plugins that depend on the @reactioncommerce/hooks package, you will need to update or obtain updated versions that use context.appEvents instead. If you have a plugin that uses MethodHooks, update it to implement those hooks a different way. review all appEvents consumed and emitted by custom plugins. Update expected and emitted arguments. See the table. (#4915)

Multiple Payment Support

• All of the individual placeOrder* GraphQL mutations provided by the built-in payment plugins are removed and replaced with a single placeOrder mutation which supports multiple payments. Any custom payment method plugins will break due to the removal of createOrder internal mutation. Look at all changes. (#4908)

Surcharges

• When applying surcharges to certain methods, there is a delay in the update. (#4984)

Updates

• RefactorinventoryQuantity to inventoryInStock in Products collection, update if used in your codebase. (#4930)

Removals

• There is no longer a storefront catalog grid (#4973)
• There is no longer a Checkout UI (#4948)
• There is no longer a Cart UI (#4948)

New Commands

In relation to improving performance, we have added new debugging statements (#4992)!

"inspect": "node --experimental-modules --inspect ./.reaction/run/index.mjs",
"inspect-brk": "node --experimental-modules --inspect-brk ./.reaction/run/index.mjs",
"inspect-docker": "node --experimental-modules --inspect=0.0.0.0:9229 ./.reaction/run/index.mjs",
"inspect-brk-docker": "node --experimental-modules --inspect-brk=0.0.0.0:9229 ./.reaction/run/index.mjs",

Example Usage :

docker-compose run --rm --service-ports reaction yarn run inspect-brk --service-ports
docker-compose run --rm --service-ports reaction yarn run inspect --service-ports

New Documents

We have added new documentation! :

• We officially stated that reaction-platform has not been fully tested or is compatible with Windows. https://docs.reactioncommerce.com/docs/next/installation-reaction-platform
• We added a Storefront UI Development guide answering: "How do I build a storefront for Reaction or adapt my storefront to get its data from Reaction, without starting from an example app" (https://docs.reactioncommerce.com/docs/next/storefront-intro)

Feature

• feat: use .env.example files from custom plugins (#5003)
• feat: add ordersByAccountId query (#4981)
• feat: allow plugins to register functions to handle GraphQL transformation of catalog product media items (#4988)
• feat: support storing custom fields on orders when placing (#4962)
• feat: shipping Operator into 2.0 (#4967)
• feat: custom tax data part 2 (#4965)
• feat: allow tax services to add custom data to taxes (#4955)
• feat: shipping surcharges (#4829)
• feat: navigation manager UI (#4936)
• feat: make Sitemap data available via GraphQL query (#4927)
• feat: tag management operator UI (#4914)
• feat: add custom fields to order schema (#4979)
• feat: update collectionIndex util function to take options (#4950)
• feat: add envalid package (#4943)
• feat: GraphQL subscriptions (#4938)
• feat: create fulfillment surcharges (#4801)

Fixes

• fix: add tagId check to guard against undefined (#5015)
• fix: do not emit afterCartUpdate unless surcharges are updated (#5001)
• fix: properly save all customFields from tax service result (#4986)
• fix: don't crash when mediaItem.URLs is null (#4982)
• fix: addAccountAddressBookEntry mutation - set account updatedAt (#4971)
• fix: taxes not updating reactively in starterkit (#4949)
• fix: inventory is set to NaN in rare circumstances based on Migrations (#4946)
• fix: use stripe.setAppInfo to identify ReactionCommerce to Stripe (#4942)
• fix: tag bulk actions copy (#4941)
• fix: ENOSPC error with jest --watch (#4939)
• fix: tag ui bugs (#4933)
• fix: migration 56 throwing an error (#4934)
• fix: 404 from invite email link (#4919)

Refactors

• refactor: update inventoryQuantity field to be inventoryInStock (#4930)
• refactor: replace all Hooks with appEvents (#4915)
• refactor: rewrite placeOrder and support multiple payments for an order (#4908)

Chores

• chore: delete unused files (#4990)
• chore: wrong version in migration 54 & 55 file (#4940)
• chore: updated dependencies and snyk policies (#4974)
• chore: meteor and docker performance tweaks (#4992)
• chore: storefront catalog grid (#4973)
• chore: remove the cart UI (#4948)
• chore: remove the checkout UI (#4947)
• chore: update to base image 1.8.0.2 to include Kafka binary libs (#4937)

Contributors

Thanks, @rattrayalex-stripe for contributing to this release!

v2.0.0-rc.9

This is our ninth release candidate for v2.0.0 of Reaction. Please check it out and let us know what works and what doesn't for you.

This release is being coordinated with reaction-platform and is designed to work with the same versions of reaction-next-starterkit and reaction-hydra

Inventory improvements

We've made some updates to the way inventory is tracked, introducing a new inventory field: inventoryAvailableToSell. This field tracks inventory that has been ordered, but has not yet been processed and so is still counted in-stock. This number is what is displayed to customers and determines whether a product is considered "sold out" or not. The old inventory number inventoryQty has been renamed to inventoryInStock and continues to represent the inventory available in stock. For more info see #4859.

Breaking changes

Inventory

• Migration 51 has been added to attach inventoryAvailableToSell to all products / variants, to correctly calculate the numbers on parent products / variants, and to publish this data to already published Catalog items.
• currentQuantity has been marked with depreciated in the cart. This isn't a breaking change at the moment, but lays the path to remove this field and replace with inventoryAvailableToSell and inventoryInStock in the future.
• Catalog.getVariantQuantity and ReactionProduct.getVariantQuantity have been removed. Custom plugins using these methods will need to be updated. The same data returned by these methods is now on the object that was being passed into these methods as the field inventoryQuantity or inventoryAvailableToSell
• Moved isBackorder, isLowQuantity, and isSoldOut functions from the catalog plugin to the new inventory plugin. Custom plugins using these methods will need to update their import path.

Features

• feat: Add flag to enable only IDP routes (#4903)
• feat: Record plugin versions in DB and show in Shop panel (#4895)
• feat: Add support for fallback tax service (#4871)
• feat: Update to Apollo Server 2.0 (#4884)
• feat(#4848): Return only isVisible Tags, unless admin (#4879)
• feat: Support remote graphql schemas in plugins (#4870)
• feat: Support plugins directly registering React components (#4875)

Bugfixes

• fix: Password reset page not found (#4917)
• fix: add replace to remove comma from formatting (#4910)
• fix: add contentForLanguage resolver for nav item content (#4913)
• fix: Restore CORS for 401s (#4894)
• fix: Meteor method permissions fixes (#4883)
• fix: Multi-shop permission fixes (#4872)
• fix: check permissions for order workflow methods (#4863)

Tests

• test: Fix sitemaps test timeouts (#4920)

Refactors

• refactor: updates to inventory counts and statuses (#4859)

v2.0.0-rc.8

This is our eighth release candidate for v2.0.0 of Reaction. Please check it out and let us know what works and what doesn't for you.

New Bits

Operator 2.0

The core experience and UI for a shop operator using Reaction Commerce has not changed much over the last couple of years. We've been hard at work on the new and improved storefront but until now have not revealed any of our design or plans for improving the updated operator UI.

This release includes the first beta of the new Reaction operator UI. Our focus with this new operator UI has several goals. First, we’re transitioning from a single page storefront and admin experience to a full page admin experience that will be separate from the storefront. . We believe this change is necessary and beneficial for anyone operating a store that works with a large number of products and/or does a high-volume of order. This change also decouples the customer facing storefront from the operator UI. The existing UI had a WYSIWYG flavor to it where the product and catalog management was done in an interface that was identical to what the customer saw. There are some benefits to this - having a good perspective of what your customers see when you make a change - but for large catalogs, it's not very practical. In addition, we’ve received feedback that the experience could be confusing for admin users who wanted to concentrate on their admin tasks only. Once decoupled the operator UI can use 100% of the screen space for store management and operation. The change will be a big benefit to users managing large product catalogs and complex fulfillment patterns.

Right now this new operator UI is opt-in and the existing, drawer style operator experience will continue to function as it has. You can access the new operator UI by visiting /operator.

This UI should have all existing functionality baked in, but we anticipate that there may be some rough edges and from a user experience standpoint it is the first step on a longer path. The first step here has been to replicate existing functionality by moving existing components into the new layout and fixing bugs that we've found. Going forward, we'll be implementing improved UIs for many of the operator tools - Catalog Management, Inventory, Pricing, Order Management, etc.

Please file an issue for any bugs that you find, whether they be weird UI quirks or things that don't as expected.

.env file

Most services that make up the Reaction platform use a .env file in the root of the service folder to define environment variables that should be set while running. They also have a pre-build script that the reaction-platform tool runs to create or update the .env file from a .env.example file, which is committed. Until now, this project did not use .env file, so we've added one. See reactioncommerce/reaction#4826 for more details.

Improved Bits

Support for extending GraphQL enums and unions

We've updated GraphQL and GraphQL Tools to new versions and added support for extend enum and extend union. This permits extending the core schema in this way from a plugin. See reactioncommerce/reaction#4798 for more details

Developer performance

When we introduced reaction-platform and begun developing in Docker environments, we began to notice high CPU utilization that for those of us developing on OSX.

Long story short, this is an issue with filesystem operations in Docker for Mac and there's not much we can do to resolve the core issue. In development mode, we leverage Meteor to watch for file changes. By adjusting the polling interval for the Meteor file watcher, we can greatly reduce the issues introduced by Docker for Mac. We've set two environment variables in the example .env file .env.example (reactioncommerce/reaction#4826) as follows, but if these don't work for you, I'd start by adjusting the polling interval to something higher - 20000 (20s) or 30000 (30s). If you're working directly on the core reaction project, this may impact how long it takes before a change you've made is recognized and rebuilt, but that may be a small price to pay to reduce CPU burn by hyperkit. There shouldn't be any other consequences to increasing this number.

  METEOR_DISABLE_OPTIMISTIC_CACHING=1
  METEOR_WATCH_POLLING_INTERVAL_MS=10000

Breaking changes

This release contains a number of breaking changes that we've been working to get into Reaction before we cut the final 2.0.0 release. If you're planning to update an existing shop, please read through this list

Catalog

• Added a new, final param to xformVariant with the processed inventory flags (reactioncommerce/reaction#4742)

Meteor Methods

• Payment plugins that use Meteor methods for capture and refund will not be compatible with this PR. This is intentional as we're migrating toward GraphQL and away from Meteor Methods for client-server interaction. Custom payment methods will need to be rewritten to follow the pattern in #4803. (reactioncommerce/reaction#4803)
• If a custom plugin uses any of these methods, it will need to be updated. (reactioncommerce/reaction#4815)
  • shop/getBaseLanguage
  • shop/getCurrencyRates
  • shop/getWorkflow
  • getTemplateByName
  • orders/addOrderEmail
  • taxes/updateTaxCode
  • workflow/coreOrderWorkflow/coreOrderProcessing
  • workflow/coreOrderWorkflow/coreOrderCompleted
• Custom code relying on being able to call the "accounts/sendWelcomeEmail" Meteor method will break. Calls from client code must be removed. Calls from server code should be updated to import and call the util function. (reactioncommerce/reaction#4867)

Taxes

• We've created a new taxes-rates plugin in the included folder, and all features related to custom rates have been moved there. This includes the "Custom Rates" panel in tax settings; the Taxes collection and its related schemas; the "taxes/addRate", "taxes/editRate", and "taxes/deleteRate" Meteor methods, and the "Taxes" Meteor publication.
• The core taxes plugin has a new API for registering tax services (such as the included "Custom Rates" service, or a custom Avalara service for example). They are registered by passing in a taxServices array to registerPackage (example and details in #4785)
• Some tax-related fields on Cart, CartItem, Order, OrderFulfillmentGroup, and OrderItem have been moved, renamed, added, or removed. We've attempted to remove all unused fields, and group or rename other fields for clarity. One example is the taxes array, which now has a different schema and appears for individual items as well as the full cart or order fulfillment group.
• On Products documents, taxable is now isTaxable. This change had previously been made in the Catalog schema and now is made in Products to match.
• For the Custom Rates plugin, be aware that the taxCode value is now used for filtering which products should be taxed at that rate. This requires a review of all your products to ensure that they have a tax code specified, in addition to being marked as taxable. If you'd rather not do this review, you can revert to the old behavior of ignoring tax codes by editing each of your Custom Rates entries, clearing the the "Tax Code" field, and saving.
• If you are upgrading from 1.x and use only Custom Rates for taxes, data migrations should provide a seamless transition. Most tax changes are breaking only for third-party non-included tax plugins. However, please verify after upgrading that the correct tax service is active.

Address Validation

Breaking changes to how address validation works. Affects all plugins that provide address validation and all clients that validate addresses. (reactioncommerce/reaction#4767)

Configuration

• Propel was updated and any propel scripts must be updated. (reactioncommerce/reaction#4802)
• If you run Reaction locally, such as for development, you will now need to be sure there is a .env file with correct environment variables set in it. The .env.example file, with no changes, should work for most people. When running with reaction-platform, this should happen automatically. But if you've already been developing locally and you pull in this change, you'll need to run bin/setup once. You can also run bin/setup anytime you pull in the future, to add any new ENV variables. (reactioncommerce/reaction#4826)
• Docker network streams.reaction.localhost must be created, which developers can do by pulling down the latest reaction-platform and running make (or make network-create if they want to be surgical about it). (reactioncommerce/reaction#4805)

Meteor Plugins

• Custom plugins that rely on the dispatch:run-as-user Meteor package will need to find a different solution and remove the dependent code. (reactioncommerce/reaction#4825)

Features

• feat: Navigation Backend (#4683)
• feat: shipping method restrictions (#4821)
• feat: Update main Reaction app to use .env file (#4826)
• feat(tag): add Display Title to Tag (#4856)
• feat: Operator 2.0 first draft (#4800)
• feat: Deploy feature branches to ECS (#4834)
• feat: Add Order.referenceId (#4827)
• feat: Use no-meteor functions for payment capture and refund methods (#4803)
• feat: Remove unused meteor methods (#4815)
• feat: Put mongo on the streams network (#4805)
• feat: Update graphql packages to support extend enum and extend union (#4798)
• feat: Improve tax API, split out Custom Rates plugin (#4785)
• feat: Address validation GraphQL (#4767)
• feat: add isBackorder data to variants (#4855)

Fixes

• fix: Migrate existing tag nav to new navigation tree structure (#4882)
• fix: primaryShopId query fallback (#4862)
• fix: permission issues with Meteor methods for Accounts plugin (#4867)
• fix: Add migration file for plugin route name change (#4858)
• fix: CartCleanupJob (#4799)
• fix: 404 on Hydra Oauth page (#4835)
• fix: Jest integration tests (#4824)
• fix: ECS deployments (#4836)
• fix: ECS deployment: move TLS certificate ARN from propel.yaml to ENV vars (#4802)
• fix: catalog variant inventory flags always false (#4742) .. Resolves #4741
• fix: tax calculation arguments, other tax fixes (#4811)

Refactors

• refactor: shipping rules (#4789)

Performance

• perf: Add a mongodb index on Catalog.updatedAt (#4819)

Chores

• chore: use ci env var for staging url (#4885)
• chore: e2e integration for release branches (#4878)
• chore: Configure prettier arrowParens to match our eslint rules (#4876)
• chore: Add node_modules/.bin to PATH in docker (#4820)
• chore: remove unused dispatch:run-as-user package (#4825)

v2.0.0-rc.7

This is our seventh release candidate for v2.0.0 of Reaction. Please check it out and let us know what works and what doesn't for you.

Security Release

This security release addresses to potential vulnerabilities

1. We discovered a vulnerability that affects shops built on Reaction Commerce that use the Reaction-Social plugin with Facebook and the Facebook App Secret configured. More details on this issue below.

2. Remove dependency on event-stream

Event Stream Dependency Removal

This fix removes a dependency on event-stream introduced by nodemon via pstree by bumping nodemon and pstree.remy through nodemon to a version that does not include pstree.

event-stream had a malicious bit of code added to version 3.3.6 which has since been removed from github and appears to have specifically targeted copay.

v2.0.0-rc.6

This is our sixth release candidate for v2.0.0 of Reaction. Please check it out and let us know what works and what doesn't for you.

Meteor 1.8 Final

We've been using a release candidate of Meteor 1.8 in all of our 2.0 release candidates to this point - this has also included release candidate versions of Babel 7. In this release we're updating to the final version of Meteor 1.8 and Babel 7.

There are a lot of great updates that are included in Meteor 1.8 and you can read all about them in the Meteor blog. I think the one that we'll notice the most is significant improvement to build performance that. We've been focused on improving the performance and developer experience with Reaction for a while now and this update makes significant progress towards improving the developer experience and build times. Anyone who's been using Reaction for a while should notice big improvements to the amount of time it takes for the app to rebuild after making changes.

We're still working with Node.js 8.11.4 as the upgrade to Node 8.12.0 got postponed to the Meteor 1.8.1 release. If you're itching to play with it, you can run meteor update --release 1.8.1-beta.n from the directory that you've got the core reaction project installed. There may be some additional speed improvements related to Meteor's use of Fibers that come along in this version.

We've also updated the our base docker image to use Meteor 1.8 (#4760)

Email Sending

We've extracted the core email sending functionality into a new reaction-email-smtp plugin which is included and created a new sendEmail event which is emitted for each email job. The core smtp email plugin now listens for these events and sends an email if an SMTP provider is configured. By doing this we've made it possible to create plugins which send emails via an API rather than via SMTP.

The email provider config form found at Dashboard -> Emails -> Mail Provider is now also able to be overridden. Plugins can use register.js to provide a React component to use here.

GraphQL API

Added a primaryShop GraphQL query & resolver, eliminating the need to first query for the primary shop ID, followed by another query for shop by ID.

Breaking Changes

In #4749 we changed the names of our included payment method plugins. We've included a migration to automatically update any existing installation, but if you have custom code that relies on these payment method names you may need make some changes.

Fixes

• fix: keep toggles shown, width 100% in action view (#4772)
• fix: Use babel.config.js to fix Jest tests in custom plugins with package.json (#4782)

Features

• feat: decouple SMTP email sending logic from core to allow plugins to override (#4740)
• feat: Add a CORS-enabled endpoint for token refresh in Hydra plugin (#4743)
• feat: GraphQL query & resolver for loading the primary shop (#4747)
• feat: update to Meteor 1.8 final (#4753)
• feat: update to base image 1.8 (#4760)
• feat: client ui payment methods (#4749) .. Resolves #4719
• feat: added migration for adding available payment methods to shops. (#4729)
• feat: use GraphQL for payment methods operator ui (#4749) .. Resolves #4719

Migrations

• chore: added migration for adding available payment methods to shops. (#4729)

Chores

We've been ignoring some of our integration tests as the in-memory MongoDB they rely on has not been working effectively. Previously we did this by skipping our entire test:integration tests in CI, we're now just skipping the tests that are failing due to this db incompatibility and have plans to address this soon.

• chore: Skip failing integration tests (#4751)
• chore: Deploy release branches to staging ECS environment (#4758)

v2.0.0-rc.5

This is our fifth release candidate for v2.0.0 of Reaction. Please check it out and let us know what works and what doesn't for you.

Mongo replica set issue

Many people were having issues with the Mongo replica-set image starting before the Mongo database was ready. This could cause the replica-set to fail and the application to hang during startup in a development environment. This is fixed in #4748 by waiting for mongo to be reachable within the reaction container before connecting to it, and creating the DB if needed, initiating the replica set if needed, and waiting for the replica set to be OK. This fix should solve the docker-compose startup race conditions we've been seeing. (#4748)

GraphQL

We've added two new GraphQL queries for payment methods. A query paymentMethods which will list all registered payment methods and is restricted to operators and availablePaymentMethods which will list all payment methods which have been enabled. These new queries were added in #4709. We've also added a GraphQL mutation that permits an operator to enable or disable a payment method for a shop in #4739

We've updated the CartItems and OrderItems GraphQL queries to include a productTags resolver which will return the tags for the CartItem or OrderItem. The new resolvers and updated schemas were added in #4715 and #4732

There is a new GraphQL mutation for generating sitemaps generateSitemaps this replaces the sitemaps/generate meteor method. method. (#4708)

Classic Storefront UI Updates

We've replaced the customer facing Product Grid in the Classic Storefront UI with our CatalogGrid component from the Reaction Design System. This was accomplished in #4649

There's a new "Include in sitemap?" checkbox in the Product Settings when using the operator interface to edit product information. This was added to make it possible to exclude published products from the sitemap. (#4708)

Additional Plugin Capabilities

A plugin can now include a catalog object in registerPackage, with customPublishedProductFields and customPublishedProductVariantFields that are set to arrays of property names. These will be appended to the core list of fields for which published status should be tracked. This is used to build the hashes that are used to display an indicator when changes need to be published. (#4738)

A plugin can now use the functionsByType pattern to register one or more functions of type "publishProductToCatalog", which are called with (catalogProduct, { context, product, shop, variants }) and expected to mutate catalogProduct if necessary. (#4738)

nvmrc

Even though most of the development work happens in Docker, getting the right version of node available directly in the host OS is convenient for setting up eslint integration with your editor. We've added an .nvmrc file for this as we've recommended nvm for installing and managing NodeJS in our docs for some time now.

Public API Changes

We've changed the GraphQL schema for PaymentMethod@name from PaymentMethodName to String. PaymentMethodName was a subset of string and this should not cause any issues.

Breaking Changes

WE've replaced the generateSitemaps Meteor method with a GraphQL mutation. See #4708 for details.

Because we've replaced the customer facing Product Grid UI in the Classic Storefront UI, if you had any plugins which relied on specific selectors or the structure of the existing UI, those may need to be updated.

Features

• feat: payment methods (#4709) .. Resolves #4574
• feat: enable payment method for shop (#4739) .. Resolves #4718
• feat: use component library's CatalogGrid - 2.0 (#4649)
• feat: add product tags to cart items (#4715)
• feat: Add product tags to order item (#4732)
• feat: option to choose whether a product should appear in the sitemap (#4708)
• feat: add a way to extend catalog product publication (#4738)

Fixes

• fix: Auth Consent scopes issue (#4733)
• fix: 4722 compareAtPrice - convert from Float to Money (#4731)
• fix(startup): init mongo replica set after waiting for connection (#4748)

Chores

• chore: add .nvmrc configuration file (#4744)

Docs

• docs: Link readers to Reaction Platform install instructions (#4724)
• docs: fix jsdoc copypasta on waitForReplica checkWaitRetry (#4723)

v2.0.0-rc.4

This is our fourth release candidate for v2.0.0 of Reaction. Please check it out and let us know what works and what doesn't for you.

Improving Jest test performance in CI

We started seeing unit tests timing out in CI in the morning on Friday October 5. It doesn't appear that this was caused by a change in our jest version as we were able to reproduce the issues on older branches which were previously passing. This is resolved in #4176 by changing our test:unit script in package.json to run jest with the --maxWorkers=4 flag. This resolved our issue with tests timing out, and improves test performance in CI overall. This is suggested in the troubleshooting jest here: https://jestjs.io/docs/en/troubleshooting.html#tests-are-extremely-slow-on-docker-and-or-continuous-integration-ci-server

Checkout Totals

There were some cases in the Classic Storefront UI where there would be a discrepancy between the total calculated on the server and the price calculated by the client. This is not an issue in the Next.js Storefront as all price values are calculated on the server. This is resolved in #4701

Bugfixes

fix: round total when verifying it on order create (#4701) .. Resolves #4684

Chores

fix: limit jest maxWorkers to 4 to improve CI perf (#4716)

v2.0.0-rc.3

This is our third release candidate for v2.0.0 of Reaction. Please check it out and let us know what works and what doesn't for you.

A few files snuck into our last release that had incorrect jsdoc syntax in the form of @return <Promise>Type The jsdoc parser is unable to parse any return type starting with a < and throws an error. This error is thrown during the Deploy Docs CI step and causes that step of the CI to fail. This is resolved in #4704 by fixing the jsdoc to use the correct Promise syntax @return Promise<Type>

Bugfixes

• fix: resolve errors in jsdoc Promise returns (#4704)

v2.0.0-rc.2

This is our second release candidate for v2.0.0 of Reaction. Please check it out and let us know what works and what doesn't for you.

OAuth Flow

• Get the auth URL connected to the Login request from Hydra. Get the loginAction field and pass it in the UI route query param (?action={loginAction}) to serve as state info to the Login component.(#4651)
• Update the Auth components to show appropriate form fields based on route query param (e.g ?action=signin)(#4651)
• Update the SignIn and SignUp core components to have a new hasSwitchLinks prop. This will determine if link to toggle between SignIn and SignUp views should be displayed. It defaults to true (so previous behaviour is kept - no breaking change)(#4651)
• Update Auth container for OAuth IDP flow with hasSwitchLinks=false. This makes the state of the form depend on ONLY the route query (#4651)
• Fix the Hydra session feature. Now, when a user who already signed in (and is sill within the set HYDRA_SESSION_LIFESPAN), tries to login again, we won't show the login form again.(#4651)
• Add /logout endpoint for Consumer apps (like Starterkit) to call to delete user sessions from Hydra. The delete session endpoint in Hydra lives on the Administrative port (4445), so we are not exposing it to Consumer apps to consume directly.(#4651)

Taxes

If item.tax did not exist the getTaxTotal was returning NaN which would show up in cart totals. This was introduced in #4664 and is resolved in #4670

Operator UI for editing product information

On the PDP, when typing a tag name in the admin sidebar, a console error would appear: Uncaught (in promise) TypeError: Cannot read property 'getShopId' of undefined at getShopLang (helpers.js:118). This was because Reaction was undefined when getShopLang() would run. This is resolved in #4673

Fixes

• (fix) Properly return 0 when no tax items are present (#4670)
• fix: Show correct form state during create account oauth flow (#4651)
• Fix: console error when typing a tag name on PDP (#4673)
• fix: discounts and profile orders in 2.0 (#4674)
• fix: orders dashboard layout issue (#4688) Updated a few panel styles to fit within the viewport better and not end up behind the "modal overlay"

Chores

• chore: updating get in touch link (#4676)
• chore: fix broken link in README to schema docs (#4672)

v2.0.0-rc.1

This is our first release candidate for v2.0.0 of Reaction. Please check it out and let us know what works and what doesn't for you.

In many ways this may better mark the beginning of a new way to develop for Reaction rather than the end of a big development cycle. Make no mistake, there are some pretty great things that v2.0.0 includes - for example, our GraphQL API now covers the basic commerce flow, from browsing a catalog all the way through checkout. However, this release is also bigger in many ways that just this repository. Much of our work over the past several months has gone into repositories other than this primary /reaction one.

We've created a component library called the Reaction Design System which we're announcing the initial "alpha" for. While it's still subject to change, there are a lot of very useful commerce focused components that we've built that live there. We'll have a link to the styleguidist playground up soon where you can play with and read the docs for each component.

Our new GraphQL API has enabled us to build a new UI Client for Reaction that we're calling our NextJS Starter Kit. This new UI client provides a reference storefront implementation that communicates with the Reaction API exclusively via GraphQL, eliminating some of the sluggishness that was associated with our Classic UI built on Meteor. This new client is built with NextJS and provides Server Side Rendering (SSR) out of the box, as well as (Segment compatible analytics event tracking)[https://segment.com/docs/spec/ecommerce/v2/]. We'll recommend this as the best way to build a storefront UI for Reaction going forward.

We're also introducing a new OpenID Connect OAuth2 Service which uses Hydra to enable our new UI Client to leverage our existing Meteor based Identities and roles.

These services all run together to form the Reaction Platform (working title, subject to change) - and we've got a new project called Reaction Platform which will help you get everything connected and launched together.

This changelog may feel somewhat insignificant because in part, we've been releasing bits of what is becoming 2.0.0 over the last several releases and much of the new development is happening outside of the /reaction repository.

Marketplace Updates

When multiple shops match the searched domain, prioritize the Primary Shop. This is important when searching for "shop settings" which are only stored on the Primary Shop (e.g., smtp settings).

Breaking Changes

From #4622

• Orders-related GraphQL schemas and significant changes to the Orders MongoDB schemas to better match GraphQL. See the diffs for the schema files. Two changes of note are that order.items and order.billing arrays no longer exist. Instead, each item in order.shipping has an items array and a single payment object on it. The payment object is also flattened and unused properties have been removed from it.

• context.queries and context.mutations are no longer namespaced. This simplifies things and makes it possible for one plugin to overwrite another plugin's functions if necessary.

• Some Meteor methods are removed:

  • cart/copyCartToOrder (replaced by createOrder mutation)
  • cart/submitPayment (replaced by createOrder mutation)
  • discounts/transaction
  • discounts/calculate
  • discounts/codes/credit (replaced by a function registered with the same name using functionsByType)
  • discounts/codes/discount (replaced by a function registered with the same name using functionsByType)
  • discounts/codes/sale (replaced by a function registered with the same name using functionsByType)
  • discounts/codes/shipping (replaced by a function registered with the same name using functionsByType)
  • shipping/updateShipmentQuotes
  • shipping/provider/toggle
  • shipping/rates/add (replaced with createFlatRateFulfillmentMethod GraphQL mutation)
  • shipping/rates/update (replaced with updateFlatRateFulfillmentMethod GraphQL mutation)
  • shipping/rates/delete (replaced with deleteFlatRateFulfillmentMethod GraphQL mutation)
  • taxes/calculate (replaced by non-Meteor getFulfillmentGroupItemsWithTaxAdded)
  • taxes/setRateByShopAndItem (replaced by non-Meteor getFulfillmentGroupItemsWithTaxAdded)
  • notification/send (replaced by non-Meteor createNotification function)
  • notification/delete (was unused)
  • stripe/payment/createCharges (replaced by placeOrderWithStripeCardPayment and placeMarketplaceOrderWithStripeCardPayment GraphQL mutations)

• shipping/updateParcelSize Meteor method is renamed to shop/updateDefaultParcelSize and moved to core/shop service

• Meteor UI client checkout code now places orders using GraphQL

• Add orderById GraphQL query

• The "afterCartUpdate" hooks are now called with just (updatedCart) rather than the redundant (updatedCartId, updatedCart)

• The way that orders are placed is now different. See "Order Changes" heading

• Orders can no longer be created without an email address

• The process by which plugins are asked to provide available fulfillment methods + quotes for them is changed. Rather than calling registered hooks, it calls all functions registered with the name "getFulfillmentMethodsWithQuotes" (See getFulfillmentMethodsWithQuotes.js)

• The "example" payment method form is now an "IOU" form that collects only a full name. It previously had a fake credit card form, which might have been misleading. Now it is clear that it's for demo and trial purposes only. Also, this new form is in React.

• Some unused (by core) functions have been removed from the cartOrder.js transforms that are available on Cart and Order documents in Meteor.

Previously client code would tell the server to "copy cart to order". Now, the orders plugin is mostly unaware of what a cart is. The client is responsible for converting a cart (which is a work-in-progress order) into the OrderInput schema and placing an order using that.

Related to this, payment information is now never stored on the cart. It is collected during checkout and sent with the placeOrder call. An order will only be placed if charges are successfully created using the provided payment details.

The orders service is largely unaware of how payment is done, and there is no generic placeOrder mutation. Instead, plugins that provide payment methods are expected to provide GraphQL mutations that allow you to place and pay for an order using that method. Most of the logic is shared, and is encapsulated in a createOrder mutation that the orders plugin provides. But each payment method plugin wraps the createOrder mutation to handle payment specifics.

All Meteor UI checkout code is updated to place orders using the new GraphQL mutations. The Meteor methods formerly involved in placing orders and payments are removed.

There are currently three included payment methods, each with their own place order mutation:

placeOrderWithExampleIOUPayment
placeOrderWithStripeCardPayment
placeMarketplaceOrderWithStripeCardPayment

For production, use placeOrderWithStripeCardPayment. placeOrderWithExampleIOUPayment is included for demo purposes and does not require any external services. placeMarketplaceOrderWithStripeCardPayment is part of the "marketplace" plugin, which is not fully implemented or supported. Each payment method has its own checkout UI component, which collects whatever information it needs securely.

We've updated the password reset flow to use a full page in #4637

• Move previous Password Reset modal to a dedicated page on /reset-password/:token
• Rename the affect components to not have modal suffixes
• Show a message on successful reset of the password (previously, the modal closes)

In #4613 we've renamed the Docker network on which GraphQL enabled web services are attached to api.reaction.localhost Networks in the Docker environment should be named as *.reaction.localhost. The localhost TLD is reserved and guaranteed to not conflict with a real TLD.

• To enable network communication, projects communicating with Reaction's GraphQL server must be on the api.reaction.localhost Docker network.
• PRs related to reactioncommerce/reaction#4447 should be coordinated.

We've moved the SMS schema to the SMS package in contrib in #4566

Features

• feat: Prioritize Primary when multiple Shops match domain (#3528)
• feat: Setup IDP flows for Hydra auth (#4627)
• feat: Update GQL server to use Hydra Auth token (#4626)
• feat: Use new CLI tool "propel" to deploy services to ECS (#4623)
• feat(GraphQL): Place orders using GraphQL (#4622)
• feat(GraphQL): Add GraphQL via plugin, reorg files into final 2.0 plugin patterns (#4622)
• feat: 2.0 migrations (#4648)
• feat(GraphQL): add Account.primaryEmailAddress resolver (#4647)
• feat: Update Reset Password modal to a full page route (#4637)

Fixes

• fix: apply requested sort to Cart.items in GraphQL resolver (#4624)
• fix: cart item attributes (#4607)
• fix: startup error before primary shop is created on initial startup (#4602)
• fix: Update detailView when its data changes (#4659)
• fix: fix README broken links, update copy (#4632)
• fix: sidebar actions not opening on product grid (#4641)
• fix: Ensure MongoDB replica set is ready before start (#4636)

Chores

• chore: Rename the reaction-api Docker network (#4613)

Refactors

• refactor: Remove unused schemas (#4566)
• refactor: remove all grid positions code and UI (#4628)

v1.17.1

Security Release

This security release addresses to potential vulnerabilities

1. We discovered a vulnerability that affects shops built on Reaction Commerce that use the Reaction-Social plugin with Facebook and the Facebook App Secret configured. More details on this issue below.

2. Remove dependency on event-stream

Event Stream Dependency Removal

This fix removes a dependency on event-stream introduced by nodemon via pstree by bumping nodemon and pstree.remy through nodemon to a version that does not include pstree.

event-stream had a malicious bit of code added to version 3.3.6 which has since been removed from github and appears to have specifically targeted copay.

v1.17.0

This release contains mostly bug fixes, many of which are focused on Marketplace implementations. Thanks to @pmn4 for contributing many of the marketplace fixes and additions.

There's also a little bit of cleanup of unused code in this release. This will likely be our last release on the 1.x line as our new work is focused on our 2.x version.

Features

• feat: Prioritize Primary when multiple Shops match domain (#3528)

Fixes

• fix: custom tax rates not applied (#4806)
• fix: console error tag name error pdp .. Resolves #4776 (#4790)
• fix: email settings update on cancel (#4792)
• fix: update detailView when its data changes (#4791)
• fix: submitting the template edit form now works .. Resolves #4774 (#4780)
• fix: edit groups panel (#4771)
• fix: add translated text for adding user to group by admin (#4562)
• fix: Hide Action View if Product Settings panel open (#4433)
• fix: Import getSlug instead of using this.getSlug (#4547)
• fix: Product Visibility for Marketplace Shops (#4425)
• fix: cart item attributes (#4607)
• fix: startup error before primary shop is created on initial startup (#4602)
• fix: avoid infinite looping when taxes are enabled (11e95ba) .. Resolves #4620
• fix: limit jest maxWorkers to 4 to improve CI perf (cd76a50)

Refactors

• refactor: Remove unused schemas (#4566)

Chores

• chore: Rename the reaction-api Docker network (#4613)
• chore: Use new CLI tool "propel" to deploy services to ECS (#4623)

v1.16.0

GraphQL

Features

• feat: return absolute media URLs from GraphQL (#4565)

Meteor App

Features

• feat 4571 Replace all Meteor.userId() with util function (#4582)
• feat: Improve animations and dynamically import animation libraries to reduce bundle size (#4500) .. Resolves #4441

Fixes

• fix: reaction error swallowing (#4592)
• fix: update file-collections dependency from 0.5.0 to 0.6.0 (#4589)
• fix: null check in email validation (#4520) .. Resolves #4502
• fix: Add missing Shops.layout migration (#4609) .. Resolves #4608

v1.15.0

Sitemap Generator

A sitemap generator plugin that creates and stores XML for a sitemap index, as well as sitemaps for tag pages, PDPs, and arbitrary URLs that can be added via an event hook.

There is a recurring job that runs every 24 hours (the specific interval can be changed) that generates the sitemaps. There is also a button to manually trigger a refresh, at Dashboard -> Shop -> Options - along with a notification that appears when it's completed.

Use our GraphQL API for the Product Grid within the Meteor App

As part of our push towards our GraphQL API, we've started to leverage the API inside of our existing Meteor app. This release converts our customer facing product grid from using Meteor Pub/Sub to consuming data from our GraphQL API instead. This is the first step in an ongoing initiative to start using the GraphQL API inside of our existing monolithic commerce application. See #4481 for a list of files changed.

GraphQL Checkout

This release includes the first set of GraphQL APIs designed for stepping through a checkout. While we've started to consume this API within our Storefront Starter Kit, these APIs should be treated as unstable and subject to change. We've added mutations for setting an anonymous email - setEmailOnAnonymousCart and selecting fulfillment options - selectFulfillmentOptionForGroup.

A note on fulfillment options Fulfillment options are what we're calling what used to be shipment options. In order to prepare ourselves for several types of fulfillment that do not necessarily include shipping, we're updating the checkout through order models, methods, and now our GraphQL API to be capable of grouping items into "Fulfillment Groups". This opens the door for several new types of fulfillments down the line such as In Store Pickup, Digital Downloads, Digital Key Generation, and anything else you can think up. We're not actively building any of these different fulfillment types into core, but want to ensure that it's possible and there's a clear direction to do so.

Breaking Changes

• If a plugin adds an "afterCartUpdate" hook, it will no longer be called. Change the plugin code to use appEvents.on("afterCartUpdate" instead. (#4535)
• If a plugin creates or updates a cart, be sure it calls appEvents.emit("afterCartCreate") or appEvents.emit("afterCartUpdate"), respectively, passing the proper arguments. If you do this within an appEvents.on hook for the same event, be sure to wrap the call in conditional logic to avoid an infinite loop. (#4535)
• We've refactored the Shipment schema to remove the items property. This will cause a breaking change for plugins expecting the items property to be there. Such plugins should be updated to use a combination of itemIds and the main items list. (#4531)
• Removed requiresShipping prop from products and catalog products. This has been replaced by an array supportedFulfillmentTypes. Reaction's core admin interface did not provide a method for setting this prop, and we've left the supportedFulfillmentTypes out of the exiting operator interface. This change will emable us to show a "Shipping"/"Pick Up" selector for other items down the road. Will also permit creation of digital fulfillment types, etc. (#4554)
• The last argument of the setShipmentMethod Meteor method now expects just the method ID rather than the whole method object. Core client code has been updated, but you should update any custom code that calls this method.
• Removed the resetShipmentMethod Meteor method
• The cart/setAnonymousUserEmail Meteor method is removed. This does not break any core behavior, but it might require updates to any custom plugins.

GraphQL DevServer

Features

• feat(GraphQL): update fulfillment options for group (#4538)
• feat(GraphQL): Add resolver for Cart.totalItemQuantity (#4533)
• feat(GraphQL): add resolver for Cart.checkout (#4507)
• feat(GraphQL): Replace "cart/setAnonymousUserEmail" Meteor method with setEmailOnAnonymousCart mutation (#4564)
• feat(GraphQL): Implement selectFulfillmentOptionForGroup mutation (#4548)

Fixes

• fix(GraphQL): Fix CartItem.currentQuantity (#4508)

Meteor App

Features

• feat: Convert product grid to consume GraphQL data (#4481) .. Resolves #4480
• feat: Fulfillment improvements (#4554)
• feat: Plugin for auto-generated sitemaps (#4413) .. Resolves #4353

Performance

• perf: improve orders sub speed by rearranging pipeline (#4555)
• perf: Move formatPhoneNumber (and libphonenumber-js) server-side to reduce client bundle (#4517) .. Resolves #4516

Fixes

• fix: for sidebar unable to be opened (edge condition) (#4546) .. Resolves #4545
• fix(marketplace): Default to Primary Shop when no domains match (#4544)
• fix: sync lowInventoryThreshold number between variants and child options (#4519)
• fix: Product prices showing as $NaN.undefined on the customer product grid (#4518)

Refactors

• refactor: Refactor cart / fulfillment hooks (#4535)
• refactor fulfillment items (#4531)
• refactor: resolve reaction error (#4494) .. Resolves #4477
• refactor: Dynamically import Swiper to reduce client bundle size (#4515) .. Resolves #4514

Chores

• chore: Added production bundle size check to CircleCI (#4521)

Contributors

• Thanks to @pmn4 for contributing to this release 🎉

v1.14.1

Patch release

Resolves issues found after releasing 1.14.0 - one causing jsdoc to fail during CI builds for the master branch, and another where method hooks were running incorrectly occasionally for catalog/publish/products and accoutns/addressBookAdd. See specific PRs for more details.

Meteor App

Bugfixes

• fix: Ensure method hooks always run with correct timing (before and after method) (#4537) .. Resolves #4437
• fix: jsdoc promise returns (#4539)
• fix: Null Guarding in GroupsTableCell (#4440)

Contributors

Thanks to @pmn4 for contributing to this release 🎉

NPM Package Version Changes

There are no dependency changes in this release

v1.14.0

Removing Optional Plugins

As part of our focus simplifying the core Reaction application and improving performance, we've made the decision to remove optional plugins from the core application. From our blog post on this topic:

It’s about quality over quantity. As a part of our initiative to simplify Reaction, we’re focusing on providing one reference application per feature and moving all others over to community-sponsored packages. We’ll be migrating packages, APIs, and schemas over to npm. It’s a standard approach to package management, one that improves the developer experience overall.

Here’s how it will look:

Category	Reaction default(s)	Community package(s)
Payments	Stripe, example payment package	PayPal, Authorize.net, Braintree
Taxes	Flat rate	Avalara, TaxCloud, TaxJar
Shipping	Flat rate	Shippo
Connectors	CSV connector	Shopify connector

As the first step of this process we've moved a number of packages from the https://github.com/reactioncommerce/reaction repo to independent repositories in the new https://github.com/reaction-contrib organization. You can install these packages by following the instructions located inside of each new repository. Once installed they should work as they did in v1.13. Any issues you have with updating these packages should be filed in the repos created for these packages and not in the core Reaction repo going forward. If you're interested in contributing to or helping to maintain any of the packages that we've moved to reaction-contrib, please reach out to @zenweasel and he can get you setup.

The list of packages that have been removed in this release is as follows:

• Shopify
• TaxCloud
• Avalara
• Authorize.net
• Paypal
• Braintree
• TaxJar
• Advanced Inventory Management
• Shippo
• SMS
• Discount Rates (unused, not the same as our current discount codes)
• Logging (unused by core application)

This work is listed as a breaking change. If your application relies on any of these packages, you will have to install them independently of Reaction going forward. This release will not destroy data associated with these plugins, so you should be able to safely update without losing information. However, please be sure to test this for your specific application before deploying to production and as always, backup your data before updating versions.

GraphQL Cart

This release contains the Cart and Checkout GraphQL schemas along with several cart queries and mutations. We're starting to make some changes to the core cart schemas for Reaction and the process that we use to create and identify carts.

One of these changes is when we create a cart for a customer. To this point, we've created a cart document for each and every visitor to a Reaction storefront. Going forward we'll be creating carts on demand. This means that a customer will not have a cart associated with them until they first add a product to the cart. This is how we've architected the GraphQL API to work and we've made some changes to the legacy Reaction cart system to put it in sync.

We're signifincantly adjusting the Cart schema as well. The best way to understand all of this will be to read through the updated GraphQL Cart Schema in #4307 and #4390 but I'll try to note some things to be aware of going forward.

A cart will have either an account associated with it or may be anonymous.

A cart will have an array of items associated with them. As we will be lazy in creating carts, when the cart is created this array of items will have at least one item in it. We do not destory carts if a customer removes all items from a cart, so it is possible that there will be an empty array of items inside of a cart.

One of the major changes to carts is related to how we store information necessary to create an order from a cart. We're introducing a new field checkout to the cart schema which you can dig into in #4309. This will be where fulfillment information, payment information, addresses and any other information necessary to process a checkout will be stored.

Recognizing the need to be able to handle orders which have items that require different types of fulfillment, we're organizing items into what we're calling "Fulfillment Groups." The most basic example is that a fulfillment group could be a group of items that is getting shipped to a specific address. For an order with n items, there can exist up to n fulfillment groups within that cart. This specific release doesn't introduce any new functionality for adding new types of fulfillment groups or splitting a single cart into multiple fulfillments, but it does lay the groundwork for splitting orders, creating new fulfillment types such as an in store pickup, ship to store, digital downloads, or generated license keys.

We're currently mapping this new GraphQL Schema to the existing Reaction Simple Schema, but will be transitioning all of our existing schemas to match (more or less) our new GraphQL schemas going forward.

A cart will still be associated with a single shop. This is consistent with current behavior.

There are two GraphQL Queries for fetching carts, one for getting anonymous carts anonymousCartByCartId and one for getting account carts accountCartByAccountId

This release introduces GraphQL Mutations for creating carts, adding items to carts, removing items from carts, updating cart items, and reconciling carts when a customer with an anonymous cart logs into an account.

ReconcileCarts is a new method which replaces and extends our previous mergeCarts method with additional functionality. ReconcileCarts has 3 modes: merge, keepAnonymousCart, and keepAccountCart. merge is the default mode and works identically to how the existing mergeCarts method works, where the anonymous cart is combined with the account cart, items are deduped, and quantities are incremented to match the combined qty of the items in the carts. keepAnonymousCart will keep only the items and the checkout information in the anonymous cart, and keepAccountCart will do the same but for the Account Cart.

Breaking Changes

Meteor App

File Organization

• We've moved all files from /server into plugins. All imports with paths that begin with /server will need to be changed for any custom code or community plugins. See the file changes in https://github.com/reactioncommerce/reaction/pull/4366/files to see examples of changing import paths from /server to relevant plugin paths.

Cart

• A cart is not created until items are added. Previously a cart was created for all users, including anonymous users, immediately if one was not found. This is not a breaking change for the core app, but any custom plugins may have code that will need to be updated to handle the possibility of there not being a cart.
• Update the signature of most cart methods to take an optional cartToken string param. Update all places that call these methods to pass in the token for anonymous carts.
• Carts and Orders no longer have userId. They now have accountId. Core client code has been updated, but custom code will need to look up the account for the user and then look up the cart or order from that.
• The CartItem SimpleSchema no longer includes variants and product, i.e., the entire variant and product objects are not copied to the cart item. Instead, certain properties that are needed are copied directly to the CartItem object. For example, item.productSlug. See the updated schema.
• cart/removeCart Meteor method behavior is the same as before, but the return value is now { cart }
• The signature of the "cart/setAnonymousUserEmail" method has changed. It now takes cartId, token arguments. The client code that calls it has been updated, but any custom code calling it will need to be updated.
• Accounts.loginWithAnonymous is no longer available to client code. This was only used in one place, and similar logic has replaced it in that spot.
• workflow/pushCartWorkflow and workflow/revertCartWorkflow methods now require that you pass in the cartId rather than guessing which cart you intend.
• In general, be aware that cart.accountId may now be null. Previously, it would be set even for anonymous carts, to the account for the user with "anonymous" role. For now, order.accountId is still set after an anonymous order is placed.
• The "Reaction.sessionId" stored ID is now used only for auto-login of anonymous users. It is not used by any of the cart code. Also, the "Sessions" collection is no longer written to or published to clients. It will not be dropped automatically, but you can drop it if you no longer need it.

Checkout

• Stripe checkout now uses Stripe Elements - for more details see #4325

Tags

• We're now limiting the tags publication to show only tags from the current active shop. This is more of a clarification of how this was supposed to work, but if you depended on all tags being published, this will cause unexpected behavior. See #4206 for specific changes.

Other

• Removal of previously included ancillary packages listed in the "Removing Optional Plugins" section
• The function createCatalogProduct has been moved into it's own file. This function was not being exported and should not create any issues, but be aware.
• The Catalog schema has been changed. It was in a "use at your own risk" state before this, but if you've been using it you may have to migrate some data
• We've removed the core plugin Logging which was used only by the Avalara plugin to this point. If you relied on this plugin, you'll need to reinstall it.

GraphQL

• In the GraphQL context, there is no longer a methods object. Instead you can call any method with context.callMeteorMethod(name, ...args).
• In the GraphQL context, context.queries is now namespaced by which plugin the queries come from. For example, context.queries.userAccount is now context.queries.accounts.userAccount.

Notable Features

Deploy to Heroku Button

We've added a deploy to Heroku button which should appear in the project readme now. You can now deploy Reaction to Heroku by clicking the "Deploy to Heroku" button and then filling out hte information required by Heroku.

Hashing Products

We're now hashing products to determine when a product changes that have not been published to the Catalog. This shows up as an indicator on the publish button when viewing a product that has unpublished changes.

Serve js and css from CDN

We now provide an option to serve the bundled javascript and css files from a CDN. See #4316 for more information.

robots.txt

We've added a permissive default robots.txt file. This file permits all bots to crawl and disallows bots from crawling /resources

GraphQL DevServer

Features

• feat: GraphQL Cart Schema (#4307)
• feat: GraphQL Cart checkout schemas (#4390)
• feat: Add anonymousCartByCartId GraphQL query (#4382)
• feat: createCart mutation, addCartItems mutation, and related cart/order schema changes (#4412)
• feat: Meteor-free addressBookAdd method and GraphQL plugin reorg (#4167)
• feat: Add resolveAccountFromAccountId resolver (#4495)
• feat: remove cart items (#4474)
• feat: update cart items quantity (#4472)
• feat: create reconcileCarts mutation (#4443)
• feat: Add accountCartByAccountId resolver (#4427)

Meteor App

Features

• feat: Shippo address validation (#4086)
• feat: Use token to create Stripe charges (#4325)
• feat: Create deploy to heroku button (#4320)
• feat: enable oplog in development Docker Compose config (#4420)
• feat: Create product hash of published product properties (#4336)
• feat: added CDN settings to reaction (#4316)
• feat: Indicator to notify of pending product changes not yet published to catalog (#4383)
• feat(marketplace): Limit Tags Publication to Those for the Current Shop (#4206)
• feat: add robots.txt file (#4370)
• feat: Remove account from anon carts, don't use session for carts (#4496)
• feat(marketplace): Consideration for Marketplace Shops on Different URLs (#3332)

Fixes

• fix: update and pin to latest version of sharp package (#4466)
• fix: Use hashtags and tagIds to form tags obj (#4415) .. Resolves #4414
• fix: Marketplace Settings (#4334) .. Resolves #4333
• fix: update dependencies (#4444)
• fix: Invalidate circleci caches (#4432)
• fix: changing product handle throws 404 (#4403) Resolves #4023
• fix: Tax and inventory toggle switches do not work (#4445) Resolves #4401
• fix: Taxcloud with marketplace setup. (#4140) Resolves #4089
• fix: Options now have parent's taxCode (#4182) Resolves #4141
• fix(marketplace): also send notification to shop owners upon order creation (#4295)
• fix: not publishing customer accounts (#4402) .. Resolves #4374
• fix: Can't save discount codes (#4410) .. Resolves #4408
• fix: Discount Codes React Table Not Rendering Correctly (#4411) .. Resolves #4247
• fix: Unable to save custom tax rate (#4405) .. Resolves #4396
• fix: low quantity/sold out flags not saving correctly in db (#4342)
• fix: Scrolling to bottom adds more products to the view (#4243) .. Resolves #4090
• fix: remove react-addons-create-fragment (#4164)
• fix: change session active product when adding new product (#4313)
• fix: missing styles on refund popover (#4300) .. Resolves #4005
• fix: fix permissions of shop social settings (#4312)
• fix: Archived products not being removed from Catalog (#4392)
• fix: Default settings for parcel size (#4083)
• fix: Update prerender.js (#4331)
• fix(marketplace): Product Visibility for Marketplace Shops (#4259) .. Resolves #4092
• fix: mislabeled schema (#4371)
• fix: ActionView Component Typos (#4439)
• fix: Cannot set replyTo or other field options when using Reaction.Email.send (#4380) .. Resolves #4343
• fix: migration error preventing app startup (#4491)
• fix: add media information to Variants and Options (#4468)
• fix: Publish button infinite loop bug (#4488)
• fix: client errors related to domain lookup changes (#4471)

Performance

• perf: Dynamically import Moment locales to reduce client bundle size (#4455) .. Resolves #4454
• perf: Improve app startup time when large number of Accounts/Users exists (#4449) .. Resolves #4384

Refactors

• refactor: Use new Reaction component library components for the SMS settings form (#4318)
• refactor: Remove "Catalog" from menu (#4385)
• refactor: Move all /server files to plugins (#4366)
• refactor: Update Catalog Schema (#4421)

Plugin Migration

• refactor: Remove Shopify plugin (#4395)
• refactor: Remove TaxCloud plugin (#4428)
• refactor: Remove Avalara plugin (#4398)
• refactor: Remove Authorize.net plugin (#4310)
• refactor: Remove Paypal plugin (#4339)
• refactor: Remove Braintree plugin (#4351)
• refactor: Remove disabled TaxJar plugin (#4348)
• refactor: Remove inventory package (#4388)
• refactor: Remove shipping-shippo plugin (#4460)
• refactor: Remove SMS plugin (#4451)
• refactor: Remove unused discount-rates plugin (#4458)
• refactor: remove unused logging (#4476)

Chores

• chore: CircleCI step for deploying to an existing ECS cluster (#4487)
• chore: make the snyk-security step a dependency for the docker-build step; s… (#4446)

Contributors

Thanks to @pmn4 and @hrath2015 for contributing to this release 🎉

NPM Package Version Changes

This is a list of all new, changed, and removed dependencies that exist in our dependency graph for a production build. This does not include dev dependencies.

New Dependencies

@babel/[email protected]
@babel/[email protected]
@emotion/[email protected]
@emotion/[email protected]
@emotion/[email protected]
@emotion/[email protected]
@emotion/[email protected]
@emotion/[email protected]
@emotion/[email protected]
@reactioncommerce/[email protected]
@types/[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

Updated Dependencies

[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected] /Users/spencer/reaction/reaction
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

Removed Dependencies

42-cent-base
42-cent-util
@braintree/wrap-promise
@sindresorhus/is
@types/node
UNMET PEER DEPENDENCY graphql@^0.10.0 || ^0.11.0 || ^0.12.0
aphrodite
array.prototype.flatten
authorize-net
base64url
braintree
buffer-crc32
cacheable-request
chain-function
clone-response
connect-query
dateformat
debuglog
deprecate
duplexer3
from2
got
has-symbol-support-x
has-to-string-tag-x
http-cache-semantics
into-stream
is-object
is-plain-obj
is-retry-allowed
isemail
isurl
joi
json-buffer
json-stable-stringify
jsonify
jsonwebtoken
keyv
lodash.isboolean
lodash.isinteger
lodash.isnumber
lodash.once
lowercase-keys
nexmo
normalize-url
p-cancelable
p-is-promise
p-timeout
paypal-rest-sdk
pop-iterate
prepend-http
q
react-addons-create-fragment
react-addons-pure-render-mixin
responselike
rootpath
scmp
shippo
shopify-api-node
sort-keys
stopcock
string-hash
timed-out
topo
twilio
url-parse-lax
url-to-options
weak-map

Metrics

You don't improve what you don't measure. In efforts to improve the size of our bundles, the time to first paint, time to interactive, and overall performance of our applications, we're starting to report on bundle size and some performance metrics in every release. With effort and persistence, we'll see these numbers improve over time.

Bundle Size

We measure bundle size by building the application using meteor build and then measuring the js and css bundle size with the command wc -c /path/to/js-bundle-file.js

JS Modern Browsers: 4872kb JS Legacy Browsers: 5104kb CSS All Browsers: 392kb

v1.13.1

This release exclusively includes a patch update to Meteor from 1.7.0.1 to 1.7.0.3

This release should be installed by anyone on Reaction 1.13.0 and includes an important security update to Node, updating to version 8.11.3 of Node, which is an important security release.

The underlying meteor-babel npm package has also been updated to version 7.0.0-beta.51.

Security

• security: Update to Meteor 1.7.0.3 (#4368)

v1.13.0

Removal of Legacy Product Revision Control system

The major change in this release is that we've removed the existing revision control system in favor of publishing Products to the Catalog. The existing revision control system contained some powerful ideas, but was complex and intertwined into many areas of the app that were not directly related to Product. By removing the old revision control system, we've paved the way to substantially improve product grid performance, especially for Operators and we've simplified the product publication logic.

This removes all code, hooks, collections, and packages related to revision control.

Breaking changes:

• Any custom packages that depend on the Revision control system.

• Operators will no longer be able to "undo" changes to a product. Instead products are published through the catalog

• Any unpublished changes to products will be lost when upgrading to 1.13.0. In this release, it's possible that if you were to downgrade that you would see the unpublished changes again, but that may cause unexpected behavior. We recommend either publishing or discarding any changes to your products before upgrading to this release.

• Similarly, any products that have been created but not published will demonstrate unexpected behavior. To avoid this undesirable behavior, publish any newly created, unpublished products prior to upgrading to this release.

• All plugin authors will need to update your package.json with a change to the babel config similar to what was done here

Update to Meteor 1.7

This update brings some enormous improvements to the amount of time it takes to rebuild the application in development after making a file change. In some (less than perfectly scientific) tests that I ran testing file changes between 1.7 and 1.6.1 I saw 50%-90% improvements in the reload time. Your experience may vary depending on how much you've customized Reaction, your computer specs, and your specific development setup, but I fully expect this to be a noticeable improvement for anyone working with Reaction.

There are some early reports that the included update to the MongoDB driver may have some kinks to work out, so I'd follow those issues on Meteor's repo if that's a cause for concern for you. These reports are all coming from a single person, and we haven't experienced any of these issues in particular yet, but we'll be keeping an eye on them.

We ran into a few issues with npm install that we resolved in #4317. One product that came out of this investigation was some documentation for how to properly clean up and rebuild docker images in Reaction.

To stop and clean up your images

  docker-compose down -v --rmi local --remove-orphans

To rebuild your Reaction images

  docker-compose up --build --force-recreate --renew-anon-volumes

If you only want to run Reaction and not the GraphQL DevServer

  docker-compose up --build --force-recreate --renew-anon-volumes reaction

If you only want to run the DevServer and not the Meteor app

  docker-compose up --build --force-recreate --renew-anon-volumes devserver

Meteor App

Performance

• perf: remove revision control (#4238)
• perf: update to Meteor 1.7 (#4265)

Bug Fixes

• fix: Use catalog collection for PDP (#4324)
• fix: Import fixture data only if collections empty (#4327) .. Resolves #4326
• fix: Invalid class name: .variant-list-item-{variant._id} (#4217)
• fix: NPM build issue in Docker build (#4317)
• fix: add getAutoValues: false to discounts/codes/remove (#4288)
• fix: hadolint image version (#4306)
• fix: CI step failure to tag Docker image with latest release version (#4304)
• fix: admin products publication slowness (#4260)
• fix: remove inventoryPolicy check on low inventory (#4298)

Refactors

• refactor: non meteor schemas (#4266) .. Resolves #4263

Tests

• test: new mocks factory (#4276) .. Resolves #4246
• test: run snyk when package.json has changed or base is master (#4285)

Docs

• docs(jsdoc): document all Meteor Template helpers in 1 @namespace (#3841) .. Resolves #3840

GraphQL Dev Server

Features

• feat: add Media to Tag Schema and GraphQL query (#4270)

Chore

• chore: update default GraphQL query limit values (#4297)

Contributors

Thanks to @mikeumus for contributing to this release. 🎉

v1.12.1

Bug Fixes

• fix: handle products without positions obj .. Resolves #4299

This release is a hotfix for #4299 which was discovered shortly after v1.12.0 was released.

The issue was releated to a type error that was thrown during a migration:

If any documents in Catalog collection do not have a positions property, migration fails on startup on first start after migration to v1.12.0. The migration is left locked. The error message is:

0|reaction | TypeError: Cannot convert undefined or null to object
0|reaction |     at Function.keys (<anonymous>)
0|reaction |     at items.forEach (imports/plugins/core/versions/server/migrations/25_update_catalog_schema.js:28:12)

v1.12.0

Breaking changes

We've made some significant changes to the structure of the data that we publish to the Catalog in #4218. We have created an automated migration for these changes in #4272. If you have made other changes to the catalog in your app or in a plugin, this migration may not work out of the box for you. We'd recommend migrating a test or staging instance of your application with similar data before applying this update to your production application.

From the PR notes to #4218, here's a list of the changes

Method argument change

"products/updateProductPosition" method now takes a tag ID rather than tag name as its third argument

Media change

The media property on catalog items is still an array of objects, but the structure of those objects has changed.

BEFORE:

{
  metadata: {}, // the full metadata object from the Media doc
  thumbnail: "", // a URL
  small: "", // a URL
  medium: "", // a URL
  large: "", // a URL
  image: "", // a URL
}

AFTER:

{
  priority, // copied from metadata
  toGrid, // copied from metadata
  productId, // copied from metadata
  variantId, // copied from metadata
  URLs: {
    thumbnail: "", // a URL
    small: "", // a URL
    medium: "", // a URL
    large: "", // a URL
    original: "", // a URL
  }
}

Also, the media array is now sorted in ascending priority order.

Deleted and hidden variants change

When published to the catalog, the variants array on the catalog item now includes only those variants where isDeleted IS NOT true and isVisible IS true.

Product props separated from catalog item props

Most product properties that were formerly on the catalog item itself are now moved to a product object property.

Explicit property copying

Previously all product and variant props were blindly copied into the catalog item. Now, we explicitly copy only the props we want, sometimes changing their names.

Property name changes

• variant.taxable -> variant.isTaxable
• variant.variantId added, currently the same as variant._id but might not always be. A reference back to the variant in the Products collection.
• product.taxable -> product.isTaxable
• product.productId added, currently the same as product._id but might not always be. A reference back to the product in the Products collection.
• product.handle -> product.slug
• product.hashtags -> product.tagIds

product.twitterMsg and product.facebookMsg and product.googleplusMsg and product.pinterestMsg are converted to a product.socialMetadata array like this:

socialMetadata: [
  { service: "twitter", message: product.twitterMsg },
  { service: "facebook", message: product.facebookMsg },
  { service: "googleplus", message: product.googleplusMsg },
  { service: "pinterest", message: product.pinterestMsg }
];

New Pricing Object

We've deprecated the price property on catalog products, variants, and options. There is a new property called pricing, which is a map keyed by currency code in MongoDB, and in GraphQL is converted to an array.

The GraphQL schema:

"The product price or price range for a specific currency"
type ProductPricingInfo {
  """
  A comparison price value, usually MSRP. If `price` is null, this will also be null. That is,
  only purchasable variants will have a `compareAtPrice`.
  """
  compareAtPrice: Float

  "The code for the currency these pricing details applies to"
  currency: Currency!

  """
  UI should display this price. If a product has multiple potential prices depending on selected
  variants and options, then this is a price range string such as "$3.95 - $6.99". It includes the currency
  symbols.
  """
  displayPrice: String!

  "The price of the most expensive possible variant+option combination"
  maxPrice: Float!

  "The price of the least expensive possible variant+option combination"
  minPrice: Float!

  """
  For variants with no options and for options, this will always be set to a price. For variants
  with options and products, this will be `null`. There must be a price for a variant to be
  added to a cart or purchased. Otherwise you would instead add one of its child options to a cart.
  """
  price: Float
}

These are currently mapped as follows, but in the future you will be able to have different prices per currency that your shop supports.

pricing: {
      [shopCurrencyCode]: {
        compareAtPrice: variant.compareAtPrice || null,
        displayPrice: variantPriceInfo.range,
        maxPrice: variantPriceInfo.max,
        minPrice: variantPriceInfo.min,
        price: typeof variant.price === "number" ? variant.price : null
      }
    },

Catalog Item props

All product props other than positions are now on the product object, so there are a few new properties on the catalog item itself:

• _id (this is no longer the same as the product ID)
• shopId (stays here AND on product obj)
• createdAt
• updatedAt

ReactionProduct.getTag

The ReactionProduct.getTag helper function is renamed to ReactionProduct.getTagIdForPosition and returns the tag ID rather than name. If there's no tag in the route path, it returns "_default" rather than the lowercased shop name.

Meteor App

Features and Improvements

• feat: Catalog schema changes (#4218)
• feat: Catalog schema migration (#4272)

Bugfixes

• fix: Limit Products when in Edit Mode (#4256) .. Resolves #4254
• fix: added event param to onBlur method in numericInput component (#4251)
• fix: Load more products working now (#4233) .. Resolves #4090
• fix: show .00 cents for whole-dollar amounts in price range (#4222)
• fix: get react root node correctly (#4172)

Tests

• Reduce Risk of Test False Positives (#4033)

Chores

• chore: Update to our latest eslint config (#4282)
• chore: resolve snyk issues (#4257)
• chore: Use NPM random package (#4208)

GraphQL Dev Server

Features and Improvements

• feat: catalog price sort (#4255) .. Resolves #4245
• feat: devserver improvements (#4220)
• feat: add description and name to shop query (#4209)
• feat: catalogItem GQL query (#4200) .. Resolves #4106
• feat: create connection/edge resolver helper (#4225)

Bugfixes

• fix: hasNextPage being false, even with a known next page (#4249)
• fix: improve hasNext/hasPrevious (#4231)
• fix: pagination (#4228)
• fix: first value pagination (#4204) .. Resolves #4186

Chores

• chore: access media through devserver app (#4216)

Docs

• docs: remove community calls from readme.md (#4279)
• docs: clean up jsdoc comments, namespace organization (#4213)

Contributors

Thanks to @pmn4 for contributing to this release! 🎉

v1.11.0

The major focus of v1.11.0 has been on our GraphQL API. We've added most of the queries and mutations that are necessary for building a headless client to interact with Accounts. We're actively doing experiments on how we'll recommend connecting to this GraphQL client and we'll start publishing some of our initial client apps to interact with this GraphQL API in the near future.

GraphQL

• feat: GraphQL remove account from group mutation (#4102)
• feat: GraphQL invite shop member (#4103)
• feat: GraphQL add account to group mutation (#4095)
• feat: GraphQL address remove mutation (#4087)
• feat: GraphQL address update mutation (#4077)
• feat: GraphQL address add mutation (#4068)
• feat: GraphQL roles query (#4076)
• feat: GraphQL group and groups query (#4053)
• feat: GraphQL connections and devserver app (#4048)
• feat: GraphQL add primaryShopId query (#4175)
• feat: GraphQL add setAccountProfileCurrency mutation (#4094)
• feat: GraphQL tags query (#4165)
• feat: GraphQL Update queries to not need Meteor (#4097)
• refactor: GraphQL transform types using resolvers (#4166)
• refactor: GraphQL switch to .graphql files for schema (#4169)
• docs: GraphQL add some missing schema docs (#4160)

Features

• feat: styling shop slug box for Shopify (#4091) .. Resolves #2780
• feat: convert AddressBook to react (#4054) .. Resolves #3518
• feat: Accept Shop Data when Inviting Shop Owner (#3456)

Refactors

• refactor: extract schemas API to an npm package (#4149)
• refactor: extract Logger API into new npm package (#4110)
• refactor: extract Hooks API to an npm package (#4147)
• refactor: remove unused Themes collection (#4198)

CI

• chore: Add snyk check to CI config; Bump base version (#4002)

Fixes

• fix: preference writing in marketplace (#4111)
• fix: onClick to image too (#4067) .. Resolves #4058
• fix: wait for slugify to show up before returning slug (#4049)
• fix: use numericInput for pricing (#3999) .. Resolves #3821
• fix: credit card accepts invalid expiration date (#3795)
• fix: check permission before publish (#3885) .. Resolves #3754
• fix: multiple instances of Components.Login causes a browser warning (#4044)
• fix: Currency as object (#4156) .. Resolves #4152
• fix: no access-denied in "accounts/setProfileCurrency" for self (#4199)
• fix: client side validation on address book (#4183)
• fix: Fix Simple Schema runtime errors (#4190) .. Resolves #4173
• fix: Remove _sleepForMs from tests (#4161)
• fix: #4037: Paginate and Filter Orders Subscription on Admin Dashboard (#4038)
• fix: for "Product publication handle regex match issues with similar product handles (#4065)
• fix: #4057: Admin should have media editable (#4072)
• fix: Make shipping discount code case-insensitive (#4082)
• fix: Error when enabling Shopify inventory hooks (#4148)
• fix: Correct some translation errors for i18n/it.json (#4174)
• fix: inventory badge component added #4032 .. Resolves #4009

Docs

• docs(jsdoc): #3840 DOM module - add @memberof, @method (#3842)
• docs: #3840 jsdoc - document fixtures (#3873)

Contributors

Thanks to @pmn4, @glmaljkovich, and @awles for contributing to this release

v1.10.0

Collection Hooks | Breaking Change!

The biggest change in 1.10.0 is the removal of the meteor-collection-hooks package. If your app or plugin is dependent on collection hooks, we'd recommend refactoring to eliminate the need for those types of hooks. If you're not up for refactoring you can just add that package back into your app though you'll lose some of the benefits that Reaction will see by eliminating that dependency. The removal of this package is a breaking change for any plugin that depends on collection hooks or uses the direct method to update a collection. For example, Products.before, Products.after, and Products.direct will no longer work. These hooks have all been migrated to our event hook system. If you were using Collection hooks to perform an action that you cannot perform in 1.10.0 with the current set of event hooks, please file an issue and we can determine if we need to add additional event hooks. This change should lead to much simpler code that is easier to understand.

New GraphQL API

In addition to a few performance updates, refactors, and bug fixes, this release starts the rollout of our GraphQL API. Until further notice, this GraphQL API should be considered a prototype and should not be used for production. If you're interested in following along with our GraphQL work, tracking our GraphQL issues is probably the easiest way for now.

In short, this release adds a prototype GraphQL server running in the Reaction project with the following urls exposed:

/graphql - The GraphQL endpoint.
/graphiql - The GraphiQL user interface.

We'll be incrementally adding functionality to this GraphQL endpoint, but this release serves as the starting point for our GraphQL api.

GraphQL

• feat: GraphQL Prototype (#3898) .. Resolves #3935, Resolves #3928, Resolves #3910
• feat: GraphQL Jest testing pattern (#3995) .. Resolves #3936
• feat: Create GraphQL viewer query (#4019)
• feat: Create GraphQL account query (#3991)

Refactors

• refactor: remove collection hooks in search mongo package (#3889) .. Resolves #3866
• refactor: remove collection hooks for Products collection (#3825)
• refactor: remove media hooks (#4035) .. Resolves #3994
• refactor: hooks in the inventory package to use Hooks.Events (#3887)
• refactor: remove collection hooks package (#4036)

Performance

• perf: Memoize/Cache getShopId to Reduce DB Load (#3510) .. Resolves #3507

Fixes

• fix: typo fix (#4000) .. Resolves #3975
• fix: Browser console warning when beginning checkout (#3980)
• fix: PDP Image gallery does not handle portrait sized images well (#3993)
• fix: Cloning products is not reactive (#3964)
• fix: Uploading Product Image (#4029)
• fix: ProductsContainers are not replaceable (#4025)
• fix: ProductGridItem is not replaceable (#4027)

Tests

• CI: Run Jest and Meteor tests in parallel (#4030)

Docs

• docs(jsdoc): namespace MethodHooks into its own JSDoc section. (#3844) .. Resolves #3840

v1.9.0

This release contains a lot of fixes, some of them performance related and several enormous refactors. The three biggest changes are:

1. We've migrated from the Meteor version of Simple Schema to the npm version. See notes in the breaking changes section below.
2. We've dropped our dependency on the deprecated Meteor-CollectionFS package. We've replaced it with an npm package we've created called reaction-file-collections
3. We've created a new catalog collection for use on the Product Grid when viewed by a consumer or other user without a product admin role

There's a full list of changes and fixes below, as well as detailed explanations of potential breaking changes and what you might need to do to migrate

BREAKING CHANGES

This is a breaking change for any plugin that implements or modifies a schema based on the Meteor simple-schema package.

From the Simple Schema update

This PR updates the aldeed:simple-schema Meteor package dependency to instead depend on the simpl-schema NPM package, which is the newest release of the same library. As part of this change, there are several breaking changes and other gotchas to be aware of.

IMPORTANT! The NPM package does not play nice with the previous Meteor package. After updating to this Reaction release, run the app one time, and then look at the .meteor/versions file. Make sure that aldeed:simple-schema is not listed. If it is there, that is because you depend on another Meteor package that depends on aldeed:simple-schema. You will have to update or remove any such packages (with meteor remove / meteor add) until aldeed:simple-schema disappears from your .meteor/versions file. Search your app for any import { SimpleSchema } from "meteor/aldeed:simple-schema" lines that you have added in your custom code, and replace them with import SimpleSchema from "simpl-schema" Be aware that the package name does not have the "e" on "simpl". (There is a different NPM package called simple-schema with the "e", and that is NOT the one you want.) If you have your own custom schemas, refer to the SimpleSchema changelog to update them for the breaking changes: https://github.com/aldeed/meteor-simple-schema/blob/master/CHANGELOG.md#200 If you use attachSchema in your code, be aware that passing an array to attachSchema will no longer work. You should first merge all the schemas and then pass the combined schema to attachSchema

Please read the PR if you need more details Use NPM SimpleSchema rather than Meteor #3331

From the removal of CollecitonFS

If you've saved the file URLs anywhere, they're now different.

/assets/files/:collectionName/:fileId/:filename

becomes

/assets/files/:collectionName/:fileId/:primaryStoreName/:filename

and

/assets/files/:collectionName/:fileId/:filename?store=storeName

becomes

/assets/files/:collectionName/:fileId/:storeName/:filename

We've deleted some unused Blaze templates rather than update URL handling within them:

• shopBrandImageOption
• ordersListItems
• select
• upload
• productMetaField
• productMetaFieldForm
• metaComponent
• productDetailEdit
• productDetailField
• productImageGallery
• imageDetail
• imageUploader
• productSocial
• variantList
• variant
• Media-related publishing is changed and improved:

Publications have been added, removed, or changed:

• CartItemImage publication is removed
• CartImages now takes an ID
• Added ProductGridMedia to replace Media being included with the products publication for the grid
• Added ProductMedia
• Added OrderImages, similar to CartImages, used for order now rather than reusing CartImages

Full notes on the PR to replace CFS #3782

From the customer product catalog

The old imports/plugins/included/product-variants/containers/productsContainer.js has been renamed to productsContainerAdmin.js and a new component named productsContainer.js now handles which products container to load based on the user's permissions. Full notes on the PR #3876

From the Dockerfile updates

reactioncommerce/base:v4.0.1 removed the following:

• Removed the conditional MongoDB installation (via $INSTALL_MONGO env). Use mongo as a service in docker-compose, see example in README.
• Removed the conditional PhantomJS installation (via $INSTALL_PHANTOMJS env). If PhantomJS is required in your build, you can include it in your custom Dockerfile. Full notes on the PR

Dockerfile Updates

• Base image updated to reactioncommerce/base:v4.0.1 which has:
  • node:8.9.4 as base image (same Debian base as before, but with Node 8 preinstalled)
  • Meteor 1.6.1 preinstalled
• Multi-stage build support. This helped reduce the size of the production image by removing un-required dependencies.
• Final production bundle uses node:8.9.4-slim

Docker Compose changes

• Updated existing docker-compose.yml to serve as the config for running a local development environment.
• Added a new docker-compose-demo.yml for testing out production builds (this is the replacement for the previous docker-compose.yml).

Upgrades

• Use NPM SimpleSchema rather than Meteor (#3331)

CI

We've updated our circle ci config to use v2 of Workflows. This permits us to run additional automated tests on circle instead of using other services. We now have 6 workflow steps that must pass before a PR can be merged.

Refactors

• refactor: rename Import to Importer (#3613) .. Resolves ##1364
• refactor: convert search modal wrapper to React (#3853)
• refactor: replace CFS (#3782)
• refactor: customer product grid publishing (#3876) .. Resolves #3662
• refactor: remove unused collection hook (#3950)

Fix

• fix: inventory updated on shopify sync (#3897) .. Resolves #3718
• fix: settings startup error (#3939)
• fix: email validation (#3899) .. Resolves #3733
• fix: change all email verification links to use tokens (#3884)
• fix: update shopId the right way. (#3947) .. Resolves #3945
• fix: migration version after SimpleSchema NPM merge (#3929)
• fix: ui glitches using dynamic merchandising (#3932)
• fix: setting or changing a products perma-link causes hard refresh (#3755) .. #2246
• fix: removing search-mongo plugin causes errors at startup (#3837) .. Resolves #3797
• fix: Reaction.getShopId missing () (#3891)
• fix: added delay and loader (#3796) .. #2863
• fix: add back missing browser policy (#3894)
• fix: discount codes limits are not honored (#3824) .. #3783
• fix: remove cfs:graphicsmagick (#3869) .. Resolves #3868
• fix: password validation (#3860) .. Resolves #3854
• fix: set localstorage even when no Meteor.user exists (#3856) .. Resolves #3846
• fix: handle misconfigured Avalara api (#3827) .. Resolves #3813
• fix: fix for "capturing bulk orders throws server side error" (#3822) .. Resolves #3705
• fix: shop switcher opens off-screen (#3809) .. Resolves #3619
• fix: /shop added to URL (#3794) .. Resolves #2810
• fix: adding country code to phone number before sending SMS (#3751) .. Resolves #3597
• fix: changing the permalink before publishing a product results in "not found" (#3748)
• fix: errors when updating default shipping and billing addresses (#3802)
• fix: delayed response in localization settings (#3872)
• fix: handle integer schema type when getting form field type (#3930)
• fix: check for number if sms is enabled. (#3983) .. Resolves #3965
• fix: marketplace shipping (#3981) .. Resolves #3979
• fix: summary not shown in Invoice (#3989)
• fix: dirty badge in product grid does not work (#3984)
• fix: reactivity error when products are not published yet (#3970)
• fix: global route hooks (#3896) .. Resolves #3895
• fix: added all the missing avalara settings fields to the fieldsProps… (#3969)
• fix: publishing group related to current shop (#3943) .. Resolves #3942
• fix: break payment before sending to paypal (#3859) .. Resolves #1236
• fix: delete shipping rates one at a time (#3968)
• fix: card validator (#3892) .. Resolves #3875
• fix: can't input refund properly (#3893) .. Resolves #3703
• fix: clean paymentMethod objects before validating (#3961)
• fix: console error during checkout (#3948)

Chore

• chore: add imports/plugins/custom to eslint ignore (#3901)
• chore: update Docker base for multi-stage builds (#3653)
• chore: use circleci workflows 2 in circle config (#3959)
• chore: remove ability to load Meteor.settings from settings.json (#3951)
• chore: upgrade react-dates to 16.3.6 (#3952)

Docs

• docs(jsdoc) - document and namespace Router.Hooks methods (#3874) .. Resolves #3840

Contributors

Thanks to @pmn4 for contributing to this release!

v1.8.2

Fixes

• fix: added unique to slug (#3745) .. Resolves #2736
• fix: Correct Inventory updates when canceling an order (#3776)
• fix: bulk order status corrected (#3807) .. Resolves #3692
• fix: order refunding number input (#3826) .. Resolves #3702
• fix: Changing user currency does not update prices (#3835)
• fix: Fix invite shop owner (#3845) .. Resolves #3836

Performance

• perf: performance upgrades by refactoring shopSelectDropdown Trackers (#3651)
• perf: Improve unnecessary translation loading (#3838)

Features

• feat: Allow for ShopId when adding Brand Assets (#3529)

Refactors

• refactor: Call OrdersList as a Component (#3848)

Chore

• chore: Add CodeTriage badge to reactioncommerce/reaction (#3666)
• chore: Update React to 16.2.0 (#3801)

Docs

• docs(jsdoc): Namespace Hooks.Events methods and add examples (#3843) .. Resolves #3840

Contributors

Thanks to @pmn4 and @willmoss1000 for contributing to this release

v1.8.1

Fixes

• (fix): email status (#3781) .. Resolves #3701
• (fix): cannot search accounts in search modal (#3829)

v1.8.0

Meteor 1.6.1

This release upgrades Reaction to Meteor 1.6.1

This is a possible BREAKING CHANGE. We've done our best to keep core reaction backwards compatible with this release, but as this update includes bumping to Babel 7, if you have plugins that depend on Babel 6, they will break. The Meteor 1.6.1 announcement or release notes are the best places to go for help debugging problems specific to Meteor introduced by this release. Additionally, you may want to check out Babel's own guide on Upgrading to Babel 7 or Planning for Babel 7

The biggest change in this release is that we're upgrading to Babel 7.

"@babel/runtime": "7.0.0-beta.38",

and in our dev-dependencies

"@babel/cli": "7.0.0-beta.38",
"@babel/core": "7.0.0-beta.38",
"@babel/preset-react": "7.0.0-beta.38",
"babel-preset-meteor": "7.0.0-beta.38-1"

Our babel presets now looks like this:

"presets": []

Yes, we've removed stage-2 and env from our presets. That's recommended as meteor now includes babel-preset-meteor

Please see the PR #3615 for even more detail on what has changed in the update to Meteor 1.6.1

ESLint

This release introduces the following changes to our .eslintrc file

jsx-a11y

We've added the recommended set of rules for jsx-a11y. Reaction has always maintained a commitment to accessibility and adding this rule set provides linting rules to help enforce Aria and a11y compliance.

"extends": [
  "plugin:jsx-a11y/recommended"
],

Base rule set

We've added the following base eslint rules. You can find their descriptions and examples of failing and passing code here: https://eslint.org/docs/rules/

"array-bracket-spacing": ["error", "never"],
"array-callback-return": ["error", { "allowImplicit": true }],
"arrow-body-style": ["error", "as-needed", { "requireReturnForObjectLiteral": false }],
"arrow-parens": [ "error", "always", { "requireForBlockBody": true }],
"no-await-in-loop": "error",
"no-bitwise": "error",
"no-case-declarations": "error",
"no-confusing-arrow": ["error", { "allowParens": true }],
"no-empty-pattern": "error",
"no-lonely-if": "error",
"no-mixed-operators": ["error", {
  "groups": [
    ["%", "**"],
    ["%", "+"],
    ["%", "-"],
    ["%", "*"],
    ["%", "/"],
    ["**", "+"],
    ["**", "-"],
    ["**", "*"],
    ["**", "/"],
    ["&", "|", "^", "~", "<<", ">>", ">>>"],
    ["==", "!=", "===", "!==", ">", ">=", "<", "<="],
    ["&&", "||"],
    ["in", "instanceof"]
  ],
  "allowSamePrecedence": false
}],
"no-multi-assign": ["error"],
"no-multi-spaces": ["error", { "ignoreEOLComments": false }],
"no-plusplus": "error",
"no-prototype-builtins": "error",
"no-tabs": "error",
"no-undef-init": "error",
"no-unneeded-ternary": ["error", { "defaultAssignment": false }],
"no-unsafe-finally": "error",
"no-useless-computed-key": "error",
"no-useless-concat": "error",
"no-useless-constructor": "error",
"no-useless-escape": "error",
"no-void": "error",
"object-curly-newline": ["error", { "ObjectExpression": { "multiline": true, "consistent": true }, "ObjectPattern": { "multiline": true, "consistent": true } }],
"object-property-newline": ["error", { "allowAllPropertiesOnSameLine": true }],
"operator-assignment": ["error", "always"],
"prefer-destructuring": ["error", {
  "VariableDeclarator": {
    "array": false,
    "object": true
  },
  "AssignmentExpression": {
    "array": true,
    "object": true
  }
}, {
  "enforceForRenamedProperties": false
}],
"prefer-rest-params": "error",
"prefer-spread": "error",
"prefer-template": "error",
"rest-spread-spacing": ["error", "never"],

Collection Hooks

We've removed the Collection Hooks package. This may be a breaking change if you're relying on Collection Hooks in your plugins. You can follow our examples to remove the Collection Hooks dependencies from your plugins or (not recommended) you can install the collection hooks meteor package back into your application without error.

We've replaced Accounts and Revisions Collection Hooks in #3642

• Replaced all Account & Revision .before, .after collection hooks to use Hooks.Events API.
• Updated Revisons.after.update(callback) to be Hooks.Events.add("afterRevisionUpdate", callback) and added Hooks.Events.run("afterRevisionUpdate", userId, revision) after every Revisons.update(...) call.
• Updated Accounts.after.insert(callback) to be Hooks.Events.add("afterAccountsInsert", callback) and added a Hooks.Events.run("afterAccountsInsert", userId, user) after every Accounts.insert(...) call.
• Updated Accounts.after.remove(callback) to be Hooks.Events.add("afterAccountsRemove", callback) and added a Hooks.Events.run("afterAccountsRemove", userId, user) after every Accounts.remove(...) call.
• Updated Accounts.after.update(callback) to be Hooks.Events.add("afterAccountsUpdate", callback) and added a Hooks.Events.run("afterAccountsUpdate", userId, user) after every Accounts.update(...) call.
• Removed .direct from any Accounts or Revisions collection calls

Breaking Changes

There are potentially breaking changes you should be aware of in this release.

• (breaking, feat) CoreLayout should probe for React component as fallback (#3524) .. Resolves #3523 A plugin which has named React components identically to Blaze templates in core may no longer work.
• (breaking, refactor) Remove unnecessary code in Media subscription. (#3558) .. Resolves #3548 We've renamed the Media subscription located in client/modules/core/subscriptions.js. This subscription's content has not changed, but is now more aptly named BrandAssets. This will only cause problems if you were subscribing to the Media publication seprately in your plugin.
• (fix): remove "admin" permission from shop manager role (#3505) .. Resolves #3541 We've removed the admin role from the default role set that is granted to the Shop Manager group. This should not affect any existing shops, but if you have plugins or users that rely on the admin role being granted to the Shop Manager group you may need to update your plugins.
• (refactor): replace imagemagick with sharp (#3631) .. Resolves #3482 This is only a breaking change if you have a plugin that depends on gm. It should be trivial to replace with sharp and this PR serves as an example of how to do so. Replace GraphicMagick/ImageMagick with sharp and remove dependency on gm Add sharp to the project and dynamically loads where necessary Update image transforms to to use the sharp() functions. Refactor the "Media" FS.Collection to map the image transforms through a buildGFS() function to create each FS.Store.GridFS collection.
• (refactor): dynamically import moment.js (#3602) .. Resolves #2635 Provides withMoment HOC to wrap components that use moment. May cause breaking changes if you relied on any of the following Blaze templates or helpers which are no longer used in core: Remove timezoneOptions Blaze template helper from client/modules/core/helpers/templates.js, as it's no longer used in any core files. Remove ordersList, orderPage/details and orderPage Blaze templates, which were replaced by React templates Move dateFormat Blaze template helper out of the global helpers, and into a specific template helper, since it's only used in one place
• Babel 7 / Meteor 1.6.1 update mentioned in detail at the beginning of these release notes.

Dependency Update

• (chore): update node dependencies (#3630)
  • Updates the following npm packages by a major version number: babel-jest, jest, libphonenumber-js
  • Updates the following npm packages bya minor version number: authorize-net, autoprefixer, babel-eslint, braintree, core-js, enzyme-to-json, enzyme, eslint-plugin-react, i18next, moment, nexmo, nock, node-loggly-bulk, paypal-rest-sdk, postcss, radium, react-dropzone, react-image-magnify, react-onclickoutside, react-select, react-table, react-tether, shopify-api-node, stripe, sweetalert2, swiper, twilio, velocity-animate

React Conversion

• We've converted the Avalara Setting page to React (see #3348)

Refactors

• (refactor): upgrade Meteor to 1.6.1 (#3615) .. Resolves #3029
• (refactor): eslint-9 and Aria (#3582) .. Resolves #3574
• (refactor): Enable eslint prefer-destructuring (#3610) .. Resolves #3573
• (refactor): Fix warnings after turning on eslint prefer-destructuring (#3598) .. Resolves #3573
• (refactor): eslint rule updates (1) (#3578) .. Resolves #3566
• (refactor): eslint errors (#3604) .. Resolves #3570
• (refactor): eslint rules 4 (#3599) .. Resolve #3569
• (refactor): fix eslint and ARIA issues for notifications (#3593) .. Resolves #3574
• (refactor): Deprecate meteor sAlert version (#3620) .. Resolves #3550
• (refactor): import Reaction from /client|server|lib/api when possible (#3611) .. Resolves unreported issue
• (refactor): remove theme editor (#3614) .. Resolves #2468
• (refactor): remove meteor-collection-hooks dependency for orders (#3639) .. Resolves #3632
• (refactor): 3636 nnnnat accounts revisions hooks events (#3642)
• (refactor): remove TranslationProvider from lower level components (#3661)
• (refactor): Converting Avalara Setting page to React (#3348)
• (refactor): Dynamically import moment.js (#3602)
• (refactor): replace imagemagick with Sharp (#3631) .. Resolves #3482
• (refactor): removed analytics plugin (#3814) .. Resolves #2301
• (refactor): use Events.Hooks instead of meteor collection hooks for cart events that trigger discount calculations (#3647)
• (refactor): replace vsivsi:job-collection for npm module @reactioncommerce/job-queue (#3641) .. Resolves #3551
• (refactor): nnnnat dynamic transliteration (#3749) .. Resolves #2634

Style

• Add CSS class to generic product fields (#3609) .. Resolves #3608

Fixes

• (fix): Undefined property: Reaction.Router.current().queryParam (#3384) .. Resolves #3496
• (fix): Cart image & Remove cart icon alignment fixes (#3740)
• (fix): Test Shopify credentials before saving. (#3468) .. Resolves #3371
• (fix): Accounts admin: Check for return value of modal dialog. (#3659)
• (fix): Display orderId instead of cartId (#3726) .. Resolves #3709
• (fix): Marketplace - allow users to become sellers (#3725) .. Resolves #3617
• (fix): substitute "-" for "/" when tagging docker image (#3739)
• (fix): Zip is optional (#3738) .. Resolves #3530
• (fix): Prevent mobile views having elements that are being cut off. (#3737)
• (fix): Added css to make OR visible (#3736) .. Resolves #3293
• (fix): Css to make whole title clickable (#3735) .. Resolves #3487
• (fix): Added space to Taxcloud notice (#3722) .. Resolves #3720
• (fix): shopify sync (#3663) .. Resolves #3502
• (fix): restore remove from cart functionality (#3657)
• (fix): Add missing address2 details (#3643)
• (fix): Cannot complete checkout on second visit when using Anonymous user (#3640)
• (fix): Fulfilling part of a multi-merchant order removes other parts of order (#3358) .. Resolves #3354
• (fix): update action view size handling to fix shipping settings cutoff (#3759) .. Resolves #3396
• (fix): Audit Product Images and update to always use optimized versions (#3730) .. Resolves #3637
• (fix): Product url should open product detail page when user clicks on an item in the cart drawer (#3758) .. Resolves #3660
• (fix): error when creating/update groups and/or group permissions for non-admin user (#3665) .. Resolves #3638
• (fix): PDP placeholde image display (#3812)
• (fix): handle invalid card details with Authorize.net (#3538) .. Resolves #3519
• (fix): can't change localization values (#3817) .. Resolves #3811
• (fix): shippo calculation error (#3774)
• (fix): Add permission checks to template method and publication (#3606)
• (fix): added currency formatting (#3808) .. Resolves #2286
• (fix): PDP placeholde image display (#3812)
• (fix): Sending the text to G+ (#3790) .. Resolves #2292
• (fix): Edit address when already present (#3788) .. Resolves #3784
• (fix): NavBar made only once (#3779) .. Resolves #3761
• (fix): Add css to truncate (#3746) .. Resolves 3499:
• (fix): Checking for shipping address and billing address (#3771) .. Resolves #3766
• (fix): remove spinner before mounting (#3806) .. Resolves #3805
• (fix): Don't use default for moment in invoice (#3816) .. Resolves #3815
• (fix): Remove methods deprecated in 1.5 (#3744) .. Resolves #2882
• (fix): handle invalid card details with Authorize.net (#3538) .. Resolves #3519
• (fix): error when creating/update groups and/or group permissions for non-admin user (#3665)
• (fix): Product url should open product detail page when user clicks on an item in the cart drawer (#3758)
• (fix): error when switching table layout in order dashboard (#3773)
• (fix): mobile subnav (#3775) .. Resolves #3679

Chores

• (chore): Build Docker image, tag, and push for every branch (#3629) .. Part of #2858 Updates our CI build process to build and tag docker images on every push to github. We are now tagging docker images with the SHA1, the git-branch-name, any git tags and tagging latest if there is a push to Master with the latest tag. You can see all of tagged docker images on our docker hub. https://hub.docker.com/r/reactioncommerce/reaction/tags/
• (chore): Add sentence to pull request template requesting images for UIX PRs (#3741)
• (chore): Update pull request template (#3687)
• (chore): update node dependencies (#3630)
• (chore): New build step "Asset Provisioning" (#3335)
• (chore): Remove methods deprecated in 1.5 (#3744)
• (chore): update README.md links to issue tags and Contributing Guide (#3700)
• (chore): add link to Contributing Guide in docs (#3688)

Performance

• (perf): dynamically import DayPickerRangeController (#3622) .. Part of #3621
• (perf): remove kadira:dochead meteor package and add needed functions to a core plugin (#3625) .. Resolves #3548
• (perf): flatten startup code and speed up translation import (#3592)
• (perf): Don't rerender on failed sign in, (#3664)
• (perf): User prefs stored in Accounts (#3463) .. Resolves #3404
• (perf): dynamically load transliteration (#3749) .. Resolves #2634
• (perf): remove meteor and babel-preset-react from babel presets (#3800)

I18n

• (i18n): Updated French translations (#3713)
• (i18n): Changed all instances of 'shoify' to Shopify (#3723) .. Resolves #3712
• (i18n): Update en.json (#3787)

Contributors

Thanks to @thetre97, @loanlaux, @wackywombaat12 and @codejockie for contributing to this release