• Home
  • >
  • DevOps
  • >
  • Bringing Clarity to the Future of Node.js Modules – InApps Technology 2022

Bringing Clarity to the Future of Node.js Modules – InApps Technology is an article under the topic Devops Many of you are most interested in today !! Today, let’s InApps.net learn Bringing Clarity to the Future of Node.js Modules – InApps Technology in today’s post !

Read more about Bringing Clarity to the Future of Node.js Modules – InApps Technology at Wikipedia



You can find content about Bringing Clarity to the Future of Node.js Modules – InApps Technology from the Wikipedia website

With the continued growth of the Node.js ecosystem, both developers and businesses have found themselves struggling with how to best curate, manage, and secure their Node modules. On today’s episode of InApps Technology Makers podcast, GoDaddy Senior Software Engineer Bradley Farias, and IBM Node.js Technical Lead James Snell were interviewed by TNS founder Alex Williams and industry veteran Darryl Taft at Node.js Interactive held earlier this month in Austin, Texas. The group discussed the need for stronger curation tools within the ecosystem, and the progression of the ECMA working group TC-39 within the Node.js community, and more.


Bringing Clarity to the Future of Node.js Modules

Also available on Apple Podcasts, Google Podcasts, Overcast, PlayerFM, Pocket Casts, Spotify, Stitcher, TuneIn

Modules present a variety of challenges when getting started with Node.js, particularly for enterprises. “It’s really hard to figure out where to start. Which modules should be used for which purposes, right? That’s kind of a big missing piece of the puzzle, is which modules are good, which are supported, which can I really depend on if I’m building a business? Being able to pick out which of those pieces are ideal is something that’s not being handled well right now,” said Snell.

Read More:   The Importance of Uptime and Efficiency in the Application Economy – InApps 2022

With no formal roadmap for how Node updates and improvements are handled, Snell went on to highlight the fact that it’s not just the Node community’s input that matters there, but the rest of the community.

“Developers are going to have to make a choice. Are they going to create a Node-style module or a TC-39 module? Which module system am I going to write my code to target? That’s going to have a significant impact on the ecosystem. In the long term, TC-39 is going to be where they’re going to want to look, but that’s going to be a long road,” said Snell.

Ultimately, as the future of Node.js modules continues to shift toward an eventual TC-39 style, many developers will find themselves having to make difficult choices while still ensuring their old modules remain supported over any possible transition period. Farias cast a skeptical outlook on the community’s pushes to advance rapidly, noting that they should focus on the issues at hand first.

“There’s something to be said about consistency. There are different approaches to this. I think if we’re going to talk about certification, we should also talk about consistency. If you can’t get the same consistent result, how can you certify something?”

GoDaddy sponsored this podcast.




Source: InApps.net

Rate this post
Content writer

Let’s create the next big thing together!

Coming together is a beginning. Keeping together is progress. Working together is success.

Let’s talk

Get a custom Proposal

Please fill in your information and your need to get a suitable solution.

    You need to enter your email to download

      Success. Downloading...