Issues
- 0
- 4
- 0
Why is it requirement for both require and import to load both kinds of modules?
#22 opened by greggman - 1
module.json
#21 opened by chharvey - 5
Let the developer decide: "import foo from 'foo.js'" means foo.js is a module
#20 opened by backspaces - 1
Create babel plugin for poly-package transition.
#17 opened by jdalton - 7
Prioritize index.js before module.js
#5 opened by pitaj - 4
- 0
- 3
Typo in agnostic-usage blurb
#14 opened by jdalton - 0
Last line of agnostic-usage.
#13 opened by jdalton - 1
- 4
package.json bin
#1 opened by boopathi - 0
- 15
4f
#10 opened by martinheidegger - 2
proposal: assume ideal future world, backwards compatibility "exercise for the reader"
#11 opened by jokeyrhyme - 3
How about to embrace webpack 2 approach?
#8 opened by alonronin - 1
module directive?
#9 opened by gibson042 - 4
Counter argument
#4 opened by prettydiff - 2
Idea on `package.json` approach
#7 opened by dead-claudia - 3
require should no longer be used
#6 opened by doodadjs - 9
Thought: default modules.root?
#3 opened by developit