For your next big project consider Vanilla JS in 2018!!!!
Blazing fast
Zero config
Per file code splitting



-
Show this thread
-
Replying to @brianleroux @slightlylate
I wonder how using react or angular works with vanilla JS today. The main issue I see with this approach is global variables are default. So one has to be careful to avoid that, and also care about loading order in the script files.
2 replies 0 retweets 0 likes -
Replying to @agmcleod @slightlylate
Both these issues are fixed! We can use <script type=module> from now on.




1 reply 0 retweets 4 likes -
Replying to @brianleroux @slightlylate
ah yeah! I kinda forgot about that lol. I should have a look to see how that functions. I’m actually pretty happy with webpack, i find it fairly reliable for me and my workflow. But eventually it’ll become less useful than built in browser support. Doesn’t hurt to get out ahead
1 reply 0 retweets 0 likes -
Replying to @agmcleod @slightlylate
They only landed in Firefox a couple of weeks ago so it's a pretty fresh win. :)
1 reply 0 retweets 1 like -
Webpack+HMR === megawin for my dev workflow. Webpack as a devtool will stay for a long time imho. Even with vanilla.
1 reply 0 retweets 1 like -
I agree! I'm suggesting folks give the vanilla platform a chance before adopting these tools. You might be surprised!
2 replies 0 retweets 0 likes
WC are landing in FF this year too; already in Chrome, Opera, UC, Samsung Internet, and Safari. You only need polyfills for FF (for a little while) and Edge/IE.
-
-
Replying to @slightlylate @brianleroux and
Problem with webComponents is lack of server side rendering
1 reply 0 retweets 0 likes -
Replying to @GundersenMarius @brianleroux and1 reply 0 retweets 0 likes
- 11 more replies
New conversation -
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.