Using Node.js require vs. ES6 import/export (2018)

Multi tool use
up vote
0
down vote
favorite
I'm starting a project using NodeJS.
I did few Javascript classes and they say, that the all browsers support ES6.
I found this question here, that was asked 3 years ago and the last answer was made in 2015 and edited in 2016.
The technology moves on pretty fast, so i would like to know, if this still the case in 2018.
javascript node.js
add a comment |
up vote
0
down vote
favorite
I'm starting a project using NodeJS.
I did few Javascript classes and they say, that the all browsers support ES6.
I found this question here, that was asked 3 years ago and the last answer was made in 2015 and edited in 2016.
The technology moves on pretty fast, so i would like to know, if this still the case in 2018.
javascript node.js
Are you targeting node.js for server side code?
– front_end_dev
Nov 10 at 15:16
Because it’s still an experimental feature in Node, I would recommend avoiding ES modules unless there’s a specific advantage you’re looking to gain with them (e.g. a static analysis tool that only supportsimport
).require
is pretty great already and you’ll certainly be using packages based around it – may as well not introduce interop considerations.
– Ry-♦
Nov 10 at 15:16
import
are still in experimental stage those things can change in future so better go with officially supportedrequire
for now.
– front_end_dev
Nov 10 at 15:20
1
This is a duplicate of previous question. If you believe answers are missing something, consider collecting some rep and putting a bounty on that question. the last answer was made in 2015 and edited in 2016 - no, last answers were posted a year ago and they are up to date.
– estus
Nov 10 at 15:21
I will use require then, i don't trust experimental things.
– User121018
Nov 10 at 15:27
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm starting a project using NodeJS.
I did few Javascript classes and they say, that the all browsers support ES6.
I found this question here, that was asked 3 years ago and the last answer was made in 2015 and edited in 2016.
The technology moves on pretty fast, so i would like to know, if this still the case in 2018.
javascript node.js
I'm starting a project using NodeJS.
I did few Javascript classes and they say, that the all browsers support ES6.
I found this question here, that was asked 3 years ago and the last answer was made in 2015 and edited in 2016.
The technology moves on pretty fast, so i would like to know, if this still the case in 2018.
javascript node.js
javascript node.js
asked Nov 10 at 15:11
User121018
133
133
Are you targeting node.js for server side code?
– front_end_dev
Nov 10 at 15:16
Because it’s still an experimental feature in Node, I would recommend avoiding ES modules unless there’s a specific advantage you’re looking to gain with them (e.g. a static analysis tool that only supportsimport
).require
is pretty great already and you’ll certainly be using packages based around it – may as well not introduce interop considerations.
– Ry-♦
Nov 10 at 15:16
import
are still in experimental stage those things can change in future so better go with officially supportedrequire
for now.
– front_end_dev
Nov 10 at 15:20
1
This is a duplicate of previous question. If you believe answers are missing something, consider collecting some rep and putting a bounty on that question. the last answer was made in 2015 and edited in 2016 - no, last answers were posted a year ago and they are up to date.
– estus
Nov 10 at 15:21
I will use require then, i don't trust experimental things.
– User121018
Nov 10 at 15:27
add a comment |
Are you targeting node.js for server side code?
– front_end_dev
Nov 10 at 15:16
Because it’s still an experimental feature in Node, I would recommend avoiding ES modules unless there’s a specific advantage you’re looking to gain with them (e.g. a static analysis tool that only supportsimport
).require
is pretty great already and you’ll certainly be using packages based around it – may as well not introduce interop considerations.
– Ry-♦
Nov 10 at 15:16
import
are still in experimental stage those things can change in future so better go with officially supportedrequire
for now.
– front_end_dev
Nov 10 at 15:20
1
This is a duplicate of previous question. If you believe answers are missing something, consider collecting some rep and putting a bounty on that question. the last answer was made in 2015 and edited in 2016 - no, last answers were posted a year ago and they are up to date.
– estus
Nov 10 at 15:21
I will use require then, i don't trust experimental things.
– User121018
Nov 10 at 15:27
Are you targeting node.js for server side code?
– front_end_dev
Nov 10 at 15:16
Are you targeting node.js for server side code?
– front_end_dev
Nov 10 at 15:16
Because it’s still an experimental feature in Node, I would recommend avoiding ES modules unless there’s a specific advantage you’re looking to gain with them (e.g. a static analysis tool that only supports
import
). require
is pretty great already and you’ll certainly be using packages based around it – may as well not introduce interop considerations.– Ry-♦
Nov 10 at 15:16
Because it’s still an experimental feature in Node, I would recommend avoiding ES modules unless there’s a specific advantage you’re looking to gain with them (e.g. a static analysis tool that only supports
import
). require
is pretty great already and you’ll certainly be using packages based around it – may as well not introduce interop considerations.– Ry-♦
Nov 10 at 15:16
import
are still in experimental stage those things can change in future so better go with officially supported require
for now.– front_end_dev
Nov 10 at 15:20
import
are still in experimental stage those things can change in future so better go with officially supported require
for now.– front_end_dev
Nov 10 at 15:20
1
1
This is a duplicate of previous question. If you believe answers are missing something, consider collecting some rep and putting a bounty on that question. the last answer was made in 2015 and edited in 2016 - no, last answers were posted a year ago and they are up to date.
– estus
Nov 10 at 15:21
This is a duplicate of previous question. If you believe answers are missing something, consider collecting some rep and putting a bounty on that question. the last answer was made in 2015 and edited in 2016 - no, last answers were posted a year ago and they are up to date.
– estus
Nov 10 at 15:21
I will use require then, i don't trust experimental things.
– User121018
Nov 10 at 15:27
I will use require then, i don't trust experimental things.
– User121018
Nov 10 at 15:27
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53240278%2fusing-node-js-require-vs-es6-import-export-2018%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
vIMwXUPNUBE6gwyg LCGp,xowmztWWQc5M,n57BYq75 8p7,Wu,SyvycFK,z1KxC,Fmc,8qWxU0blMHT2b85F,6cmGL8jE4WJt RNH7V,ARC
Are you targeting node.js for server side code?
– front_end_dev
Nov 10 at 15:16
Because it’s still an experimental feature in Node, I would recommend avoiding ES modules unless there’s a specific advantage you’re looking to gain with them (e.g. a static analysis tool that only supports
import
).require
is pretty great already and you’ll certainly be using packages based around it – may as well not introduce interop considerations.– Ry-♦
Nov 10 at 15:16
import
are still in experimental stage those things can change in future so better go with officially supportedrequire
for now.– front_end_dev
Nov 10 at 15:20
1
This is a duplicate of previous question. If you believe answers are missing something, consider collecting some rep and putting a bounty on that question. the last answer was made in 2015 and edited in 2016 - no, last answers were posted a year ago and they are up to date.
– estus
Nov 10 at 15:21
I will use require then, i don't trust experimental things.
– User121018
Nov 10 at 15:27