New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node.js Best Practices - How to become a better Node.js developer in 2018 #12

Open
gergelyke opened this Issue Dec 18, 2017 · 6 comments

Comments

4 participants
@gergelyke
Owner

gergelyke commented Dec 18, 2017

No description provided.

@gergelyke gergelyke added the comments label Dec 18, 2017

@ShrawanLakhe

This comment has been minimized.

ShrawanLakhe commented Dec 19, 2017

For me, one should start writing. i have just started blogging as well on https://www.nodexplained.com/. I find Secure Your Node.js Web Application by Karl Düüna extremely informative on security aspects of web application programming. I learnt a lot by reading this book.

@warnero

This comment has been minimized.

warnero commented Dec 21, 2017

I've been hunting and hunting to find a good answer to this. Can we use the new ES6 modules stuff? If so, how? If not, why not? I'd love to hear your answer. I just recently saw one article suggest implementing both https://gist.github.com/domenic/4748675 .

@caraya

This comment has been minimized.

caraya commented Dec 25, 2017

Look at the date for the gist, the situation has changed since then.

Jake Archibald does a pretty good job explaining current support for modules in browsers and Contentful does a good job explaining if we should stop bundling now that modules are a thing

Those articles and a crapload of testing are a good starting point.

@warnero

This comment has been minimized.

warnero commented Dec 25, 2017

Neither of those discusses what I brought up - using ES6 modulse in Node.js (unless I'm missing something). I may not have said so explicitly, but didn't think I had to since the article is titled "How to become a better Node.js developer in 2018".

@caraya

This comment has been minimized.

caraya commented Dec 25, 2017

You're right. I misread the original issue and added the wrong links to the discussion.

These are the links for Node:

Sorry about the confusion

@warnero

This comment has been minimized.

warnero commented Dec 26, 2017

Thanks! I wish some of these had shown up in my searches.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment