The new plugin system (week 22–23)
One breaking change of webpack 4 will be the new plugin system. But why changing one of the core components of webpack? Isn’t the current version working great? This post will go into more details. The problems with the current plugin system: PerformanceThe plugin system is a core component of webpack. This means plugin hooks are called pretty often. Many of the hooks are in the hot path. But the
A React And Preact Progressive Web App Performance Case Study: Treebo
Treebo is India’s top rated budget hotel chain, operating in a segment of the travel industry worth $20 billion. They recently shipped a new Progressive Web App as their default mobile experience, initially using React and eventually switching to Preact in production. What they saw compared to their old mobile site was a 70%+ improvement in time to first paint , 31% improvement in time-to-interact
Modern Modules
Re-thinking the Node.js ecosystem for modern JavaScript. A few months back I sat down to write some code. Node.js 8 had been out a while and I decided to take advantage of some of the new language features like async/await in my new code. Over the next month I wrote a half dozen small modules. By the end of the month I’d made some pretty huge changes to how I do open source development and how I s
Angular vs. React vs. Vue: A 2017 comparison
Deciding on a JavaScript framework for your web application can be overwhelming. Angular and React are very popular these days, and there is an upstart which has been getting a lot of traction lately: VueJS. What’s more, these are just a few of the new kids on the block. Javascripts in 2017 — things aren’t easy these days!So, how are we supposed to decide? A pros-and-cons list never hurts. We’ll d
How to call C/C++ code from Node.js
It might be NOT that hard as you think! Let’s see you can you can call C/C++ code or use a native library from a Node.js app. Node.js ❤ C/C++Q: Why would I need to call C/C++ code? There is half a million NPM modules, why would I need native stuff at all? A: It you don’t need any C/C++ interop right now, it doesn’t mean you won’t need it in the future. In large apps there is usually a mix of diffe
Web Scraping in 2017: Advanced Headless Chrome Tips & Tricks
Now that PhantomJS’ development has stopped, Headless Chrome is in the spotlight — and people love it, including us. At Phantombuster, scraping is a huge part of what we do, and we use Headless Chrome extensively. In this blog post, I will give you a quick tour of the Headless Chrome ecosystem and show you what we’ve learned after having scraped millions of pages. TL;DR:There are a lot of librarie
Road to webpack 4 (week 20–21)
It has been more than 2 weeks after I installed the auto-closing bot for the webpack/webpack repo. There was a warning period of 15 days. This means bot closed all inactive issue → issue count went from 700 to 500 open issues :) The process worked really great. Many incorrectly flagged issues where revived in the warning period by watchers. Reviving is pretty easy as you just have to comment on th
Async Iterators: These Promises Are Killing My Performance!
Update from 2023: Node’s performance with async iterators has improved considerably since this post was written in 2017. See the async-iteration repo for updated performance stats. Text processing in node.js has historically been both slow and cumbersome. But don’t fret, there’s hope on the horizon! The new async iterators proposal solves the “cumbersome” problem brilliantly. But sadly, it misses
Effective immediately I am stepping down from the @Nodejs TSC
https://github.com/nodejs/TSC/pull/314 NoteFirst and foremost, I am not quitting the project. I will continue my duties on the CTC, Build, and Release Working Groups. This includes the upcoming LTS releases and the stability work I have been doing with the V8 team. WhyA recent decision by the TSC leads me to believe that the Technical Steering Committee is making decisions that are not in the best
How JavaScript works: an overview of the engine, the runtime, and the call stack
As JavaScript is getting more and more popular, teams are leveraging its support on many levels in their stack - front-end, back-end, hybrid apps, embedded devices and much more. This post is meant to be the first in a series aimed at digging deeper into JavaScript and how it actually works: we thought that by knowing the building blocks of JavaScript and how they come to play together you’ll be a
How JavaScript works: inside the V8 engine + 5 tips on how to write optimized code
Couple of weeks ago we started a series aimed at digging deeper into JavaScript and how it actually works: we thought that by knowing the building blocks of JavaScript and how they come to play together you’ll be able to write better code and apps. The first post of the series focused on providing an overview of the engine, the runtime and the call stack. This second post will be diving into the i
Understanding V8’s Bytecode
V8 is Google’s open source JavaScript engine. Chrome, Node.js, and many other applications use V8. This article explains V8’s bytecode format — which is actually easy to read once you understand some basic concepts. This post is available in Chinese, translated by justjavac. Ignition! We have lift-off! Interpreter Ignition is part of our compiler pipeline since 2016.When V8 compiles JavaScript cod
Enabling brotli in your Azure CDN
TL;DR: If you are using Azure’s CDN and want to enable brotli you will need to create some custom rules that you can see at the end of the article. Addy Osmani shared this tweet about CDNs that don’t support brotli and I though it could be interesting to tell how we enabled it on Azure CDN for https://dev.microsoftedge.com. The first step is to compress the assets and configure IIS. This is relati
Even Better Support for React in Flow
The first version of Flow support for React was a magical implementation of React.createClass(). Since then, React has evolved significantly. It is time to rethink how Flow models React. In Flow 0.53.0 we are changing how Flow models React and in doing this we can provide better types for higher-order components, strict typing for React children, and fixes for a host of bugs in Flow’s React suppor
ES Modules in Node Today!
I’m excited to announce the release of @std/esm (standard/esm), an opt-in, spec-compliant, ECMAScript (ES) module loader that enables a smooth transition between Node and ES module formats with near built-in performance! This fast, small, zero-dependency package is all you need to enable ES modules in Node today 🎉🎉🎉 @std/esm used in the Node REPL after `npm --save @std/esm`A tale of two module
How do I get started with V8 development?
Are you interested in understanding more about compilers, virtual machines, JavaScript engines, and maybe even want to contribute to V8? Have you never taken a compiler course (maybe no formal CS course) or no experience in C++? Fear not, nobody was born with that knowledge. You don’t need to understand all aspects of compilers to make a contribution. Here are some resources that might help you on
Node.js Errors — Changes you need to know about
This post was written by Michael Dawson who is a Node.js Runtime Tech Dev @ IBM, #nodejs collaborator and CTC member. He originally posted this piece on the Nodejs @ IBM blog. SummaryChanges are coming to Errors thrown by the Node.js runtime. These changes started showing up in Node.js 8 and will continue to flow in during Version 9. This will impact any user whose code parses the message strings.
Linting in Flow
In the past, Flow has had to make some tough decisions about what counts as a type error, and what we should surface in our analysis. Some things, like enforcing function call parameter counts, made the cut. Others, like erring when importing types from an untyped file, didn’t. With version 0.52 we’re rolling out the new Flow linter, creating a framework that lets us report things we find that are
webpack awarded $125,000 from MOSS Program
WebAssembly Official LogoOne of the signature features of webpack is its use of the “dependency graph” to manage and bundle assets. However, every resource that is loaded into webpack must be treated as JavaScript (this includes css, images, svgs, html, etc.). Because of this, only JavaScript is a first-class module type in webpack. The downsides of this are that assets like CSS, HTML, cannot be l
WebRTC SFU における遅延の現実
よく WebRTC は遅延が少ないと言われます。P2P で直接やり取りするうえに、UDP を利用しているからです。 ただ、WebRTC は映像や音声をリアルタイムに変換し、さらに暗号化をしてやり取りを行っています。この時点でかなり重そう … という印象を持たれる方も少なくありません。特に技術に明るい人に多いように感じます さらに弊社製品は WebRTC SFU という P2P 部分をサーバ経由で行う製品のため、サーバ経由、もっと遅くなりそう。という印象を持たれます。 実際試していただくとほとんど遅延が無いことがわかると思うのですが、実際数値化したことはありませんでした。 ちょうど先程 Safari での WebRTC のテストをしていた際に、フェイクカメラが経過時間を表示していたので、配信と視聴のブラウザを並べて、スクリーンショットを持ってみました。 この時の状況としては、サーバ自体はさく
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
