Skip to content
This repository has been archived by the owner on Mar 29, 2018. It is now read-only.

Issues: esnext/es6-module-transpiler

11 Open 111 Closed
11 Open 111 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Include another (more up to date) broccoli module
#194 opened Jan 26, 2015 by ichernev
Using es6-module-transpiler in conjunction with a classes transpiler
#190 opened Jan 13, 2015 by vnys
2
Module bindings are not propagated across multiple modules when using import * as syntax bug
#189 opened Jan 2, 2015 by Pauan
@caridy
export { foo } from "./bar" does not work bug
#188 opened Jan 2, 2015 by Pauan
@caridy
Import chains do not preserve bindings across multiple files in CommonJS
#178 opened Oct 24, 2014 by eventualbuddha
NodeJS interop
#156 opened Sep 11, 2014 by guybedford
5
evaluate whether or not formatters should have access to config arguments
#141 opened Jul 7, 2014 by caridy
Discussion: vendor deps
#140 opened Jul 7, 2014 by stefanpenner
9
define guidelines for external formatters and resolvers
#131 opened Jun 25, 2014 by caridy
9
__esModule flag interop
#86 opened Dec 26, 2013 by guybedford
14
Support ExportSpecifierSet being "*". spec-compliance
#29 opened Jul 15, 2013 by domenic
10
ProTip! Mix and match filters to narrow down what you’re looking for.