Come on TC39, V8 and Node have implemented all but the most obscure parts of ES6–where is the standard for import?
NodeJS 6.1 passes 96% of ES6 tests, failing only on proper tail calls, iterator closing, and some Proxying of internal `get` calls.
But no standard is in sight for resolving resources based on the string in import statements.
View the compatibility table results at node.green
This is a demonstration of all the data your browser knows about you. All this data can be accessed by any website without asking you for any permission.
Run the test for yourself at webkay.robinlinus.com
npm decides to keep their unpublish functionality but puts in place rules to prevent breaking other packages
npm writes on their blog:
One of Node.js’ core strengths is the community’s trust in npm’s registry. As it’s grown, the registry has filled with packages that are more and more interconnected.
A byproduct of being so interdependent is that a single actor can wreak significant havoc across the ecosystem. If a publisher unpublishes a package that others depend upon, this breaks every downstream project that depends upon it, possibly thousands of projects.
Last Tuesday’s events revealed that this danger isn’t just hypothetical, and it’s one for which we already should have been prepared. It’s our mission to help the community succeed, and by failing to protect the community, we didn’t uphold that mission.
Read the whole post
All engineers write bad code. The best engineers think hard about how to refactor avoid the situation in the future.
“Excellence is never an accident. It is always the result of high intention, sincere effort, and intelligent execution; it represents the wise choice of many alternatives – choice, not chance, determines your destiny.” – Aristotle
Read more at The Full Stack
Watch out Plunkr, WebpackBin is going to redefine code sharing in 2016
A video introduction to the BETA of WebpackBin, a next generation code sharing tool.
Top features include:
- Compiling with Webpack including loaders for ES6, Typescript and JSX
- Install npm packages
- Download your working app
- Boilerplates such as a working React app
- Live reload
- Real-time code sharing, editing, and passing control
Try it out at webpackbin.com
Watch the video on YouTube
MS Edge priorities for 2016: better extension API, performance, more ES6 support, WOFF2, Web Notifications and more
We’ve been immersing ourselves in your feedback, reviewing development trends, and meeting with partners and developers around the globe to inform where we take EdgeHTML next. We want to ensure we’re focusing on the most impactful work! In the spirit of continuing our opennness, we’d like to share our priorities for 2016.
Read more from the source: Microsoft Edge Dev Blog