-
-
Notifications
You must be signed in to change notification settings - Fork 451
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
4 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
e4f1aee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these new scoped package names set in stone now, for v8? Or, is it possible these will change?
e4f1aee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we are switching to scoped packages in v7 (not v8...)
e4f1aee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@babel/core
7.x,babel-loader
8.x :Pe4f1aee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah this is part of the ordeal we all have to figure out that the other versions are independently versioned (since babel-loader was already v7) 😅
e4f1aee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, so now would be a good time to update my instructional materials for using babel? As far as the package names are concerned.
e4f1aee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the loader going to be renamed to
@babel/loader
?e4f1aee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@g0t4 I don't think we have a solid decision on that yet. For now it is
babel-loader
though.e4f1aee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be great to do that now or never.
Doing it in the future will be even more confusing for people to figure out what to use.
e4f1aee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These updates only apply to Babel 7.x beta so only people who are explicitly opting in to using the beta need to worry about it. Given that we expect that to be a relatively small chunk of people, we haven't focused on it too much at this point.
e4f1aee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The babel-notes repo seems to suggest that we're close to an RC on Babel 7.x
So I'm thinking about the 7+ scenario. i.e. is babel-loader going to be used for v8 with @babel/core v7.. and then are we going to see @babel/loader v9 in the future due to a later rename.
So another question then, is babel-loader v8 going to be finalized with babel v7? Or is it going to be a while after babel v7? And if a while, are there yet to be substantial changes to just the loader?
e4f1aee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there's some disagreement on the team about just how stable things should be before we do an RC. I personally want to fix a reasonable list of blockers first, but I believe @hzoo is more motivated to get an RC up.
I don't think I can answer that. I know that isn't super helpful, but no matter what I say we could still change our minds, so I'm hesitant to really say anything firm.
We'd aim for them to be release in parallel since we want to make upgrading as easy as we can for people. The main change that we're still exploring is changes to how caching is implemented for Babel in general, which would affect
cacheDirectory
, but otherwise I wouldn't expect sizable change within babel-loader itself, not that there is a ton of logic other than caching anyway.e4f1aee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, it's helpful to know what is outstanding.
e4f1aee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @hzoo. Why it's not
?