Node 14, Vue’s Vite, and
is-promise are in the news. We’ve got some working from home tips and unpopular opinions to share. And… shout outs! 👏
Node 14, Vue’s Vite, and
This is a nice, Smashing deep-dive by the author of React HereMaps:
The New Stack with a nice rundown of what’s new/noteworthy in Node 14. The once-an-npm-package
node-report is now mainlined, an experimental
AsyncLocalStorage API has been added, and more.
This looks like an excellent read for anyone looking to level up their fullstack JS chops:
I do React consulting and this is a showcase product I’ve built in my spare time. It’s a very good example of modern, real-world React codebase.
There are many showcase/example React projects out there but most of them are way too simple. I like to think that this codebase contains enough complexity to offer valuable insights to React developers of all skill levels while still being relatively easy to understand.
Playwright is focused on enabling cross-browser web automation platform that is ever-green, capable, reliable and fast. Our primary goal with Playwright is to improve automated UI testing by eliminating flakiness, improving the speed of execution and offering insights into the browser operation.
From the Microsoft Edge team.
At Node+JS Interactive… the talks are all quite attractive. From transpilation dread… to awesome worker threads. This conf is surely impactive!
ES Modules are unflagged in Node 13. What does this mean? Can we use them yet? We chat with Mikeal, our resident expert, and find out.
This week we chat with Matteo Collina, Technical Director at NearForm and member of the Node.js Technical Steering Committee, about his upcoming Node+JS Interactive talk on Node Streams. We talk about their creation before any standards and how they are one of the bedrock APIs used throughout the Node ecosystem. We also talk about WHATWG streams and some of their key differences, and how streams have gotten easier to work with thanks to the addition of async iterators and generators to the language.
With 35k+ stars, I might be the last one to the party on this awesome repo.
It is the largest compilation, and it is growing every week - currently, more than 80 best practices, style guides, and architectural tips are presented. New issues and pull requests are created every day to keep this live book updated. We’d love to see you contributing here, whether that is fixing code mistakes, helping with translations, or suggesting brilliant new ideas.
This is a map of known process signals with some information about each signal. Unlike
- human-friendly descriptions
- default actions, including whether they can be prevented
- whether the signal is supported by the current OS
Fuzzing for safe languages like nodejs is a powerful strategy for finding bugs like unhandled exceptions, logic bugs, security bugs that arise from both logic bugs and Denial-of-Service caused by hangs and excessive memory usage.
As we recently learned on Go Time: pessimists write tests, fuzz functions, and sleep well at night. 💤
In this episode we’re shining our maintainer spotlight on Valeri Karpov. Val has been the solo maintainer of Mongoose since 2014. This episode with Val continues our maintainer spotlight series where we dig deep into the life of an open source software maintainer. We’re producing this series in partnership with Tidelift. Huge thanks to Tidelift for making this series possible.
When talking about the Console API, newbies usually use only some functions like 👌
console.warn(), or ❌
console.error()to debug their application, while often there are many other methods which can perfectly implement our requirements and improve debugging efficiency.
This article is made to expose some of the most interesting console methods with related examples that I use while teaching at Codeworks. So let’s see a list of the 8 best functions from the Console module!
I have used
console.table a few times (totally rad), but there’s plenty of functions here that I haven’t been using (and definitely should be).
Special guest Nick O’Leary joins us this episode to chat about the Node-RED project, how it started, and the fascinating uses cases for it out in the wild. We go into some of the technical challenges behind designing easy to use interfaces for hardware, and ask Nick what the future of Node-RED looks like.
SQL injection is a serious vulnerability, effectively allowing an attacker to run roughshod over your entire database. If you’re using Sequelize, drop everything (pun unintended) and get patched up.
As a testament for Sequelize’s commitment to security and protecting their users as fast as possible, they promptly responded and released fixes in the 3.x and 5.x branches of the library, remediating the vulnerability and providing users with an upgrade path for SQL injection prevention.
If you come from Node.js, you might find that a lot of things are very similar in Deno, here we show some features that Deno and Node.js have in common, it would be great for learning purpose.
nve differentiates itself from
nvm run because it:
- can be run programmatically
- is 10 times faster
- does not need a separate installation step for each Node version
- works on Windows
- does not require Bash
- is installed as a Node module
Worth noting: this is not a full-on replacement for nvm or any other version manager. It only executes a single command with the specified Node version. But sometimes, that’s all you need. 😄
With the jumping off point of KBall’s question: “What are best practices for organizing a Node project?” Mikeal and Feross drop an incredible amount of wisdom about Node, organizing using modules, release management, deployment approaches, how to adopt change, and more.
The fastest wiki and knowledge base for growing teams. Beautiful, feature rich, markdown compatible and open source.
Run Outline yourself for free or pay for the hosted version.
KBall and Nick sync up with Node.js core contributor Ujjwal Sharma to dive deep into how to get into the world of open source software.
LGTM, but why?
Mostly because I wanted to dig deeper into node web server code, but also because I haven’t jumped onto the NoSQL bandwagon and think that web APIs are extremely useful. The result is a modest attempt at automating the CRUD boilerplate that every developer hates, while following the specs to make API consumption intuitive. I chose sqlite to keep the database side of things simple, with the intent that the API isn’t serving heavy loads.
KBall MC’d a live show at NodeConf Colombia with a panel of 4 experts from the Node community — Kat Marchán, Anna Henningsen, Ruben Bridgewater, and James Snell. It was a great discussion about the future of Node.js and the Node.js ecosystem.
You’re running out of good reasons to stay on Medium.
KBall, Emma, and Chris explain some things to each other like we’re five, bring stories of the week, and share some sweet pro tips.