Mailchimp Open Commerce is an API-first, headless commerce platform built using Node.js, React, GraphQL. Deployed via Docker and Kubernetes.
GPL-3.0 License
Bot releases are hidden (Show)
Published by spencern over 6 years ago
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
This release introduces the following changes to our .eslintrc file
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"
],
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"],
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.
There are potentially breaking changes you should be aware of in this release.
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.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.gm
. It should be trivial to replace with sharp
and this PR serves as an example of how to do so.gm
withMoment
HOC to wrap components that use moment.timezoneOptions
Blaze template helper from client/modules/core/helpers/templates.js
, as it's no longer used in any core files.ordersList
, orderPage/details
and orderPage
Blaze templates, which were replaced by React templatesdateFormat
Blaze template helper out of the global helpers, and into a specific template helper, since it's only used in one placebabel-jest
, jest
, libphonenumber-js
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
default
for moment in invoice (#3816) .. Resolves #3815SHA1
, 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/
Thanks to @thetre97, @loanlaux, @wackywombaat12 and @codejockie for contributing to this release
Published by spencern over 6 years ago
This release, along with the next one or two, make changes to our .eslintrc
file
This release introduces the following
eslint-plugin-import
https://github.com/benmosher/eslint-plugin-import/tree/master/docs/rules
We have added the following import rules:
"import/export": "error",
"import/order": ["error", {
"groups": [
"builtin",
"external",
"internal",
"parent",
"sibling",
"index"
]
}],
"import/newline-after-import": "error",
"import/no-duplicates": "error",
"import/no-mutable-exports": "error",
"import/no-named-default": "error",
These rules enforce consistency for imports and exports. Most linting errors related to these should be fairly simple to fix, but if you have duplicate or mutable exports, there may be a little bit of work to do.
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/
"block-spacing": ["error", "always"],
"computed-property-spacing": ["error", "never"],
"dot-location": ["error", "property"],
"function-paren-newline": ["error", "multiline"],
"new-parens": "error",
"newline-per-chained-call": ["error", { "ignoreChainWithDepth": 4 }],
"object-shorthand": ["error", "always"],
"operator-assignment": ["error", "always"],
"prefer-arrow-callback": ["error", { "allowNamedFunctions": false, "allowUnboundThis": true }],
"space-unary-ops": ["error", {
"words": true,
"nonwords": false,
"overrides": {}
}],
"template-curly-spacing": "error"
With all of these new rules, it's highly likely that there will be some linting errors in your own codebase when you merge this release. We recommend that you update your code to follow our new eslint ruleset. We've adopted this ruleset to ensure our code is cleaner, more readable, more consistent, and less prone to errors.
If you absolutely do not want to follow these rules or wish to follow some, you can remove or comment out any that do not fit the style you wish to follow. That should satisfy eslint. Again, we recommend updating your project to follow the new Reaction eslint rules.
We've added our security reporting instructions to our readme:
Security reporting instructions: Report security vulnerabilities to [email protected].
Thanks to @liyucun, @glmaljkovich, @duanhong169 for contributing to this release.
Published by spencern over 6 years ago
In #3552 we've removed some meteor packages that Reaction was no longer using. If you were relying on these to exist in your plugin, you'll have to add them back in.
Thanks to @nicebro @dmitry-fedyuk @wayann @pmn4 and @efalayi for contributing to this release!
Published by spencern over 6 years ago
Thanks to @loanlaux and @pmn4 for contributing to this release!
Published by spencern almost 7 years ago
Thanks to @unaheidi, @sija, and @pmn4 for contributing to this release!
Published by spencern almost 7 years ago
I Oops'd the 1.6.2 release and package-lock.json
got stuck at 1.7.0. 😞
This fixes that and bumps to 1.6.3
for both package.json
and package-lock.json
I've updated the release process docs to include tips for how to not do that again.
package.json
and package-lock.json
to 1.6.3
Published by spencern almost 7 years ago
extraneous Router code that was left over from a previous refactor, and was causing some conflicts in the client project.
The code was used to push all routes from all shops into the Router. In core Reaction, this is unneeded functionality, as we do not publish all routes from all shops, therefore the code seemed to be doing nothing in it's current state.
Thanks to @Akarshit and @wackywombaat12 for contributing to this release
There were additional updates that we were hoping to release at this time, #3367 and #3368. Those PRs contained potentially breaking changes. We have reverted those PRs and they are not included in this release. They will require more work on our Product Revisions module.
Published by spencern almost 7 years ago
Published by spencern almost 7 years ago
BlazeLayout
componentinspect
support for server debugging via chrome dev tools (See our blog post on better debugging in Reaction)Thanks to @Akarshit for contributing to this release.
Published by spencern almost 7 years ago
(fix): Validation should pass when variants don't exist (#3347)
Published by spencern almost 7 years ago
Thanks to @wackywombaat12 and @fisshy for contributing to this release!
Published by spencern almost 7 years ago
Thanks to @prosf and @Akarshit for contributing to this release! 🎉
Published by spencern almost 7 years ago
Published by spencern almost 7 years ago
Thanks to @josx and @pmn4 for contributing to this release! 🎉
Published by spencern almost 7 years ago
Published by spencern almost 7 years ago
Published by spencern almost 7 years ago
See our full Features & Roadmap
Published by spencern about 7 years ago
More bugfixes and improvements and a host of jsdoc updates and additions.
This release adds a new command that will let you generate jsdocs locally.
$> npm run docs
This command will generate docs locally on your system, you can view them on OSX/Unix by opening /tmp/reaction-docs/index.html
or visiting file:///tmp/reaction-docs/index.html in your browser.
If someone has the route for where these docs get generated on a Windows machine, I'll add that to these release notes.
On to the changelog:
Published by zenweasel about 7 years ago
(#3125) Change redirect after Shopify import
Published by zenweasel about 7 years ago