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

Why to delete your babel.config.js file ? #1

Closed
mohan-win opened this issue Apr 3, 2020 · 4 comments
Closed

Why to delete your babel.config.js file ? #1

mohan-win opened this issue Apr 3, 2020 · 4 comments

Comments

@mohan-win
Copy link

Hi, Thanks a lot for the detailed steps. Wondering why we need to delete the babel.config.js ?

@retendo
Copy link

retendo commented May 4, 2020

I second this question ;) It actually produces errors.

@martinmoec
Copy link
Owner

Sorry, i did not notice this issue until @retendo commented! You do not need to delete your babel.config.js file, but in my experience its the easiest and fastest way to get up an running. Note that i do not really have a strong Babel expertise, at all, and someone with a better understanding could probably provide you with better info and a better setup. The how-to should however be updated to reflect this, as the current wording implies deleting the file is a requirement.

@playfulThinking
Copy link

This seems to fix the errors: SAFE-Stack/SAFE-Nightwatch#74 (comment)

@martinmoec
Copy link
Owner

I have included filename: "App.js" in the splitter configuration in 8c6e340 and the error is no longer present while still including the babel.config.js file. As you can see here parts of Babels functionality is not available when the filename is unknown.

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

4 participants