@wycats Indeed -- that's kind of the point of the ".mjs" proposal: Know immediately what kind a module is by it's name.
-
-
Replying to @lbljeffmo
Yehuda Katz 🥨 Retweeted JeffMo
@lbljeffmo right, which makes this incorrecthttps://twitter.com/lbljeffmo/status/726236426510163968 …Yehuda Katz 🥨 added,
2 replies 0 retweets 0 likes -
-
Replying to @lbljeffmo
@lbljeffmo it changes the public interface of existing modules to include the kind of module, which is not true now and not necessary2 replies 0 retweets 0 likes -
Replying to @wycats
@lbljeffmo and it unnecessarily complicates migrations of users of modules that already required with .js1 reply 0 retweets 1 like -
Replying to @lbljeffmo
@lbljeffmo if a package moves to .mjs, that breaks their consumers.1 reply 0 retweets 0 likes -
Replying to @lbljeffmo
@lbljeffmo .js -> .mjs breaks node7 users; module.js breaks only node5/node6 users.1 reply 0 retweets 0 likes
@lbljeffmo Some packages wait long enough that they can migrate after they don't have to worry about old nodes anymore
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.