Big changes are coming to Deno
Deno and npm? If you remember the history of the project, you are probably scratching your head right now. After all, the story of Deno begins in 2018, when one of the developers of Node.js decided to fix the mistakes made in its design. One of the biggest mistakes mentioned at the time was the use of node_modules and the creation of npm. How is it that 4 years later Deno nevertheless gets npm support?
import express from "npm:express@5";
If we are looking for reasons for opening up to npm, let me make my personal diagnosis here. In March 2021, Deno Company was founded, fueled by nearly $5 million from independent investors. In June of this year, the project won another round of funding, this time amounting to as much as $21 million.
You can probably guess where I’m going with this. Along with external investors and customers, come expectations of growth. Deno has really built a lot around the idea of better Node.js. However, it seems that without meaningful integration with npm, further development would slow down.
If you’re interested in the details, we devoted an entire section to this technology in the 99th edition of our review. For all the forgetful and lazy, I’ll remind you that it’s supposedly a faster drop-in alternative to Node.js. In addition to performance, Bun also offers some nice features such as a much faster alternative to npm or the ability to create macros (i.e. code generated during compilation with access to the AST tree).
It is not yet known how long we will have to wait for the next version of Deno, but I am already looking forward to it. In the meantime, the team developing the project has decided to initiate so-called “Office Hours”. These will be weekly meetings where you will be able to ask your nagging questions directly. If you are interested in the details, I invite you to read the sources for more.
NativeScript Preview 2.0
The process of remotely launching an application using NativeScript Preview 2.0 is be divided into two steps. First, we download an application from the Play store, or AppStore from the developers of NativeScript. Then we run the appropriate script in the console, scan the generated QR Code and voila! A working native application appears before our eyes. What’s more, if you modify the application code in the IDE it will automatically refresh in the application.
The new preview system brings two non-obvious possibilities. First, with its help, it will be possible to build iOS apps without owning a macOS device. Second, it will be possible to simply share a developer version of the app, quite useful for demo purposes.
This is not the end of the news. NativeScript, in cooperation with StackBlitz, has prepared templates with the help of which the entire process described above is enclosed in the browser. If a few years ago, someone had told me they are writing a native application in the browser, and previewing the effects on an unconnected phone, I would have considered them crazy. Well, the future is today.
Unfortunately, there’s one fly in the ointment. For the new preview to work properly, our application can only use a finite set of native plugins. We can only count on the developers of NativeScript to keep this list updated on an ongoing basis.
Bonus: meet.js summit
meet.js is a nationwide brand that brands meetups all over Poland (personally, I regularly attend the ones held in Krakow). When they reached out to us about collaborating on a conference they were organizing, I had no doubt that it would be something you would be interested in.