Skip to content
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

Update babel-present-env and use node: 'current' as target #1051

Merged
merged 2 commits into from
Nov 17, 2016

Conversation

valscion
Copy link
Contributor

This replaces the hand-rolled node version setup with a new feature that was introduced in [email protected]: https://github.com/babel/babel-preset-env/blob/v0.0.7/CHANGELOG.md

Changes between 0.0.6 and 0.0.8 should be backwards compatible.
https://github.com/babel/babel-preset-env/blob/master/CHANGELOG.md

@gaearon
Copy link
Contributor

gaearon commented Nov 17, 2016

Thanks!

@valscion valscion deleted the update-babel-preset-env branch November 17, 2016 13:52
eXtreme added a commit to eXtreme/create-react-app that referenced this pull request Nov 18, 2016
* pull2:
  Support Yarn (facebook#898)
  Fix chrome tab reuse (facebook#1035)
  Remove unnecessary transform plugins for object spread to work (facebook#1052)
  Clears the usage of react-jsx-source & react-jsx-self (facebook#992)
  Update babel-present-env and use node: 'current' as target (facebook#1051)
  Remove redundant `function` from export statement (facebook#996)
  Add Gatsby to alternatives (facebook#995)
  Allow webpack 2 as peerDependency in react-dev-utils (facebook#963)
  Remove custom babel-loader cache dir config (facebook#983)
  Check for presence of folders before continuing eject. Closes facebook#939. (facebook#951)
  Fixes facebook#952 (facebook#953)
  Always build before deploying to gh-pages (facebook#959)
  Add collectCoverageFrom option to collect coverage on files without any tests. (facebook#961)
  Catch and noop call to open web browser. (facebook#964)
  Gently nudge users towards https by default (facebook#974)
  Enable compression on webpack-dev-server (facebook#966) (facebook#968)
  Add next.js to Alternatives
  Point people to npm Windows instructions
  Encourage people to try recent npm

# Conflicts:
#	packages/react-scripts/config/webpack.config.dev.js
#	packages/react-scripts/package.json
#	packages/react-scripts/utils/createJestConfig.js
jarlef pushed a commit to jarlef/create-react-app that referenced this pull request Nov 28, 2016
…1051)

* Update babel-preset-env to 0.0.8

Changes between 0.0.6 and 0.0.8 should be backwards compatible:
https://github.com/babel/babel-preset-env/blob/master/CHANGELOG.md

* Use `node: 'current'` as target for babel-preset-env

This replaces the hand-rolled node version setup with a new feature that
was introduced in [email protected]

https://github.com/babel/babel-preset-env/blob/v0.0.7/CHANGELOG.md
alexdriaguine pushed a commit to alexdriaguine/create-react-app that referenced this pull request Jan 23, 2017
…1051)

* Update babel-preset-env to 0.0.8

Changes between 0.0.6 and 0.0.8 should be backwards compatible:
https://github.com/babel/babel-preset-env/blob/master/CHANGELOG.md

* Use `node: 'current'` as target for babel-preset-env

This replaces the hand-rolled node version setup with a new feature that
was introduced in [email protected]

https://github.com/babel/babel-preset-env/blob/v0.0.7/CHANGELOG.md
randycoulman pushed a commit to CodingZeal/create-react-app that referenced this pull request May 8, 2017
…1051)

* Update babel-preset-env to 0.0.8

Changes between 0.0.6 and 0.0.8 should be backwards compatible:
https://github.com/babel/babel-preset-env/blob/master/CHANGELOG.md

* Use `node: 'current'` as target for babel-preset-env

This replaces the hand-rolled node version setup with a new feature that
was introduced in [email protected]

https://github.com/babel/babel-preset-env/blob/v0.0.7/CHANGELOG.md
@lock lock bot locked and limited conversation to collaborators Jan 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants