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

[WIP] Better .babelrc support #620

Closed
wants to merge 2 commits into from

Conversation

arunoda
Copy link
Contributor

@arunoda arunoda commented Jan 2, 2017

With this, we are only looking for .babelrc upto the closest directory with a package.json.

This will fix the .babelrc issue discussed in #560

@@ -202,7 +202,7 @@ gulp.task('release', (cb) => {
'compile',
'build',
'copy',
'test'
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently, tests are failing.
I'll work on a fix.

@arunoda arunoda force-pushed the better-babelrc-support branch from 8034978 to 8f8b5a7 Compare January 2, 2017 11:39
@@ -187,7 +193,7 @@ export default async function createCompiler (dir, { dev = false, quiet = false
resolve: {
modules: [
nextNodeModulesDir,
'node_modules'
appNodeModulesDir
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Had to set this, otherwise webpack raise issues that, it can't find next/* apis.

@@ -0,0 +1,3 @@
{
Copy link
Contributor Author

@arunoda arunoda Jan 2, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is just to to fool our .babelrc finding logic to stop here.

@nkzawa
Copy link
Contributor

nkzawa commented Jan 2, 2017

I'm not sure if we shoud do this since it mean to change the behavior babel users might expect.

@arunoda
Copy link
Contributor Author

arunoda commented Jan 2, 2017

Yeah. I am not sure about this either.
But if this an issue, we might can do something.

Let's keep this open until it's really really needed.

@rauchg
Copy link
Member

rauchg commented Jan 5, 2017

For now, we'll fix our examples, and re-consider this if it creates problems for others. I'll favor less code an maintain the (undesirable!) babel default

@rauchg rauchg closed this Jan 5, 2017
@arunoda arunoda deleted the better-babelrc-support branch January 6, 2017 00:02
@arunoda arunoda restored the better-babelrc-support branch January 6, 2017 00:02
@lock lock bot locked as resolved and limited conversation to collaborators Jan 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants