-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: babel transform-runtime bug #69
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Less code is better 😎
@@ -8,8 +8,12 @@ | |||
"url": "https://github.com/okgrow/merge-graphql-schemas.git" | |||
}, | |||
"license": "MIT", | |||
"engines": { | |||
"node": ">=4.8.3", | |||
"npm": ">=4.0.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need npm >= 4 ? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@xavcz Meteor is 4.8.3
, will drop it once meteor 1.6 is released.
"scripts": { | ||
"prepublish": ". ./scripts/prepublish.sh", | ||
"prepare": ". ./scripts/prepublish.sh", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is running npm publish
triggering this command normally?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@xavcz yes, npm publish
& npm install
will trigger the pre-publish
in npm 4
land. In npm 5
pre-publish only runs on publish
. See these two threads for more details npm/npm#16685 & npm/npm#10074 (comment)
Any eta on this PR getting into the production version of the module? |
Changes done in PR #71. Closing this one. |
This PR has been created to resolve a babel-runtime bug. For more details see here #68
Changes made:
prepublish
toprepare
in package.jsonbabel-preset-env
& setting target to"node: ""4.8.3"`."node: "current"
dist
folder from .gitignore so it can be tested against withoutnpm link
. Please see below in Testing.A PR we should keep our eyes on for specifying engines in
babel-preset-env
. babel/babel-preset-env#114Testing:
You can test locally by running the below command in any project that is using the
merge-graphql-schemas
package.npm install -S git://github.com/okgrow/merge-graphql-schemas#fix-babel-transform-runtime
.Additionally the branch was tested via
npm link
against a node app runningnode 8.0.0
/npm 5.0.3
&meteor npm link
against a meteor app runningnode 4.8.3
/npm 4.6.1
.I would like others to further test this as I have seen some odd behaviour with
npm link
. Remember torm -rf node_modules
.