June Engineering Monthly Round-Up

Q2 is behind us, and as we wrap up and delve into exciting projects, we continue to bring you the most noteworthy updates from the engineering world. In this roundup, we look at what’s new with some tools we currently use, notes from the ones we’re watching, interesting reads, and more. So let’s take a look at what we were reading, watching, and discovering this past month.

News & Exploration

The massive bug at the heart of the npm ecosystem

Npm is one of the biggest package managers for the JavaScript ecosystem alongside Yarn and PNPM. But this does not mean it's the better and most secure system. An ex-staff Engineer from the npm CLI team goes into the issue when installing a package can lead to insecure installs and execution of malicious scripts.

Styled-components big release

Styled-components is a go-to tool for engineers to `style` their components in their apps. Now there's a new version of the package (v6). Before updating make sure you go through the FAQs to see the breaking changes.

Vercel with the updates

Vercel (the company behind Next.js) has released a software development kit for AI apps, built with React and Svelte. This means that while integrating any LLM to your project by using OpenAI, LangChain, or Hugging Face, you don't need to go through a long development cycle to ensure the integration works properly. Read all about Vercel AI SDK.

Nest.js upgrades to v10

Nest.js one of the Node.js backend frameworks, and it just got updated to v10. Updates include bringing SWC (Speedy Web Compiler) to compile TypeScript, Redis wildcard supports, dropping Node 12 support, and upgrading the TypeScript version. Read all about the upgrades in the article above.

Read & Watch

• Cost of JavaScript 📺
• Don't be nice, be kind 📰
• Streaming on the Web 📰
• Get it done 📰

A Final Challenge

We’re closing it out with another engineering challenge!

Javascript is always an interesting language to show us its skills. Some of those skills can be good, bad, or ugly. Let's see without running this code piece if you can figure out what will be logged.

Find the answer at the end of this article!

Our Jobs

Do you want to shape the future and help build companies from scratch? Here is a list of job openings available right now at OAK’S LAB.

• Senior Frontend Engineer (React), Prague, Remote
• Tech Lead, Prague, Remote
• Senior Full Stack Engineer (Node.js / React), Prague, Remote
• Senior Backend Engineer (Node.js), Prague, Remote

That’s the end of the June 2023 Engineering Monthly Round-Up. Thank you for reading, and we hope you've enjoyed the articles, videos, and insights we shared. We look forward to seeing what this year brings our way. If you have any comments, suggestions, or other interesting material to share, please feel free to comment below or email me directly at ugur.oruc@oakslab.com. Thank you again, and we’ll be back next month.

Answer:

The answer is "Shared variable was already updated," but that does not mean this will be always true. Because JavaScript puts the `setTimeout` function on an event loop and first setTimeout will be called out first. So if you swap the orders of `setTimeout` you will receive "Shared variable not yet updated." So be careful while playing with this