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

[DEPRECATED] material-fhir-ui > [email protected]: #9

Open
awatson1978 opened this issue May 13, 2020 · 0 comments
Open

[DEPRECATED] material-fhir-ui > [email protected]: #9

awatson1978 opened this issue May 13, 2020 · 0 comments

Comments

@awatson1978
Copy link
Collaborator

Describe the deprecation
Babel presets still being used in material-fhir-ui. Need to update that build pipeline.

The Error Message
The following error message was emcounted:

warning material-fhir-ui > [email protected]: We're super 😸  excited that you're trying to use ES2017+ syntax, but instead of making more yearly presets 😭 , Babel now has a better preset that we recommend you use instead: npm install babel-preset-env --save-dev. preset-env without options will compile ES2015+ down to ES5 just like using all the presets together and thus is more future proof. It also allows you to target specific browsers so that Babel can do less work and you can ship native ES2015+ to user 😎 ! We are also in the process of releasing v7, so please give http://babeljs.io/blog/2017/09/12/planning-for-7.0 a read and help test it out in beta! Thanks so much for using Babel 🙏, please give us a follow on Twitter @babeljs for news on Babel, join slack.babeljs.io for discussion/development and help support the project at opencollective.com/babel
warning material-fhir-ui > babel-preset-latest > [email protected]: 🙌  Thanks for using Babel: we recommend using babel-preset-env now: please read https://babeljs.io/env to update!
warning material-fhir-ui > babel-preset-latest > [email protected]: 🙌  Thanks for using Babel: we recommend using babel-preset-env now: please read https://babeljs.io/env to update!

To Reproduce
Steps to reproduce the behavior:

  1. Any custom packages or plugins you may be using.
material-fhir-ui
  1. Identify the build pipeline(s) used when producing the error.
yarn install
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant