You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Fixes #5623 Summary TL;DR - basic topological ordering of plugins. Currently this is just the minimal change necessary to make class properties and decorators work (not a final approach or anything and not done yet) This PR adds 2 more properties to the Plugin object: capabilities: an array of values (currently a string, maybe better as a number/semver like in package.json) to represent what a plu
I believe most agree on: introduce a before/after key to specify which plugin ordering should error/warn if the same plugin/capability is specified twice edge case would be if you are using a plugin in a "preset" that you want to still use but want to modify it by using a plugin option - either error and not use the preset anymore or the user specified plugin should override the one used in the pr
Babel Team Meeting - 2017-06-14 Attendees Brian Ng Daniel Tschinder Henry Zhu Kara de la Marck Karl Cheng Nathan Hammond Nick Cantelmi Peeyush Sarup Banskota Sergey Rubanov Actions (Nathan) Publish meeting notes. (Henry) Document the 0.X plugin stage policy. Discussion Plugin Ordering Updates Moving to before / after . James Kyle wrote a blog post about Plugin Ordering: http://thejameskyle.com/bab
Issue originally made by @alovicu Bug information Babel version: 5.1.13 Node version: 0.10.36 npm version: 1.3.6 Description If a web page includes two (or more) different javascript applications and both of them import babel-polyfill, the second one that is executed throws the following exception and stops working: Uncaught Error: only one instance of babel-polyfill is allowed In these cases the
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く