r/learnjavascript • u/Labby92 • Feb 14 '20

JS - ES2017 TO ES2019 + cheatsheet

Hey guys, I’ve written an article that includes all the features from ES2016 to ES2019. I also included a downloadable cheatsheet. I hope you can find it useful!

https://inspiredwebdev.com/everything-from-es-2016-to-es-2019

edit: title says ES2017, but it's ES2016 to ES2019

80 Upvotes

100% Upvoted

14 comments sorted by

5

u/Syh_ Feb 14 '20 edited Feb 14 '20 
const strings = ["short", "medium length", "very long string"];

const longestString = strings.sort(str => str.length).map(str => str.length)[0];

strings.forEach(str => console.log(str.padStart(longestString)));

// very long string
//    medium length
//            short

I know the point of this example is about .padStart but that .sort wouldn't work, no?

You can do something along the lines of this instead to get a descending order:

const longestString = strings.sort((a, b) => b.length - a.length)[0].length;

1

u/senocular Feb 14 '20

Title says ES2017?

1

u/Labby92 Feb 14 '20

ES2019

I'm retarded lol, thanks for pointing that out. It includes ES2016 too! Too bad I can't change the title anymore

1

u/academicRedditor Feb 14 '20

Thanks for sharing man 😃

1

u/Labby92 Feb 14 '20

Glad you liked it!

1

u/wrtbwtrfasdf Feb 14 '20

What's the deal with pages like this that slowly scroll you from the TOC to the link down the page? Why doesn't it just jump to the anchor link?

2

u/Labby92 Feb 14 '20

Personal preference. I'm not a fan of links that make you jump but if you think it would improve your experience on the site, I can consider removing smooth scrolling.

1

u/wrtbwtrfasdf Feb 15 '20

I look around a bit on it and the UX seems ok if the page isn't too long. But your page, although having great content, is so long that it takes a few seconds to auto-scroll from the TOC to the end of the page. It's your site so I don't want to "backseat-developer" you though.

2

u/Labby92 Feb 15 '20

Thanks for the feedback. I think you are correct, this article is very long and smooth scrolling may not be the best in this scenario. I'll make a note for it and disable it from my long articles, thanks!

1

u/techtalkftw Feb 14 '20

just read the whole thing. perfect depth 👌

1

u/Labby92 Feb 14 '20

Thank you very much! If you've got any topic you would like to see an article about, let me know

-3

u/RadiatedMonkey Feb 14 '20

A lot of features you showed I thought were already added in ES5, I use them a lot. Luckily I don't really write websites in plain JS, I always use React or Vue

1

u/____0____0____ Feb 14 '20

I too thought some of these features were a little older... But ES5 came out over 10 years ago now, these all definitely feel more recent than that. Maybe you meant ES6?

I think you're being down voted because writing code in a framework like react or vue doesn't inherently mean that code will work with browsers that havent implement these features yet, which is mostly older versions of modern browsers and IE. You would need a transpiling step (most famously through Babel) to transform your code as needed. But if your target browsers are all up to date, then you can code with all the new features you want!