Best practices: Specify file extensions when using require/import in Node.js Get into the habit of using *.mjshttps://twitter.com/nodemjs/status/861841938986795009 …
-
-
Replying to @mathias
I'm not ever going to use or support the .mjs extension in my modules.
5 replies 10 retweets 53 likes -
-
Too much churn to change all the tools when it could be solved without a new extension.
2 replies 1 retweet 7 likes -
Node needs to move forward (with mjs), but I'm hopeful a consensus will emerge to do something better later! "Baby steps"pic.twitter.com/2FdJDaodUV
3 replies 0 retweets 1 like -
Replying to @xjamundx @sindresorhus and
It will never ever happen, once something is adopted in JavaScript you never go back, don't want to break the web right?
2 replies 0 retweets 0 likes
That argument is flawed: .mjs does not affect the web. Browsers don’t care about the extension.
1:17 AM - 10 May 2017
1 reply
0 retweets
1 like
-
-
Yeah but we won't want to break the node either...
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.