* PLEASE READ THIS BEFORE FILING AN ISSUE *
Follow the template below and include a codepen to ensure the quickest and most accurate response to your issue.
Please be specific, e.g. _major.minor.patch_
Please include the browser version. A user-agent string is also quite helpful.
Please include the OS version.
Please write the steps which need to be taken in order to reproduce the bug. These steps should be
as detailed as possible, e.g.
- Run the demo server
- Go to localhost:8080/textfield.html
- Tab-focus on the first text field
- Observe the component's behavior
We also have a template on CodePen which we encourage you to use to create a reproduction of
the issue. The less time it takes for us to reproduce the issue, the less time it takes to verify and
fix it!
Please describe what the component/code should be doing that it's not.
Please describe what the component/code is actually doing that's different from what it should be
doing.
If you're interested in requesting a new component or proposing UX changes to an existing
component, please read our Component Request Policy before opening an issue.
If you have an idea for a new feature, we'd love to hear about it! Please provide enough
information regarding the feature such that we'll be able to evaluate the appropriateness and
feasibility of your request. Try to be as specific as possible regarding your motivation, use-case,
and potential API or affects on other APIs (where applicable). The more detailed your proposal is,
the easier it will be for us to understand and evaluate it. This Meta.SE answer also contains great general guidelines for writing
feature requests.
If you'd like to work on a component, please ensure that you submit an Engineering Outline before
submitting a pull request. You can read more about this in our contributing docs.
MDC Web is still under active development. You can see our current progress on master as well as an overview of our architecture and practices.
Our team prioritizes responding to as many engineering and user experience questions as possible. We do not support responses to questions outside of these areas at this time.
Use this getting started guide to get the correct version of babel:
https://github.com/material-components/material-components-web/blob/master/docs/getting-started.md
The install line you want for installing babel is
npm install --save-dev babel-core@6 babel-loader@7 babel-preset-es2015 babel-plugin-transform-object-assign
Babel has updated recently and the new version is not compatible with the current version of MDC
Thanks for the response @CyborgSemon That install line gives me the same error "npm install --save-dev babel-core@6 babel-loader@7 babel-preset-es2015 babel-plugin-transform-object-assign"
im gonna try with getting started guide
Try going over the entire getting started guide in a new folder. if you have already installed babel in the folder that you ran the install command then it wont work.
So yeah. try in a new folder.
If you're using React, you may want to give MDC React a try 馃榾
Otherwise, I would suggest creating a small git repo that demonstrates the problem, and we'll be happy to take a look.
Thanks!
@moog16 is investigating this in https://github.com/material-components/material-components-web-react/issues/326
@SemihKoc you have to create a file .env.local and put this SKIP_PREFLIGHT_CHECK=true for the fix
follow
@SemihKoc you have to create a file
.env.localand put thisSKIP_PREFLIGHT_CHECK=truefor the fix
follow
Then you won't encounter other issues, That will permanently disable the messages
@SemihKoc you have to create a file
.env.localand put thisSKIP_PREFLIGHT_CHECK=truefor the fix
followThen you won't encounter other issues, That will permanently disable the messages
Do we have any special fix use-case to avoid this?
i dont know but yesterday all was working great and today i just run my app and i get that error . i already reinstall node, but its the same prob
Most helpful comment
@SemihKoc you have to create a file
.env.localand put thisSKIP_PREFLIGHT_CHECK=truefor the fixfollow