Standardizing Widget Sharing
Custom widgets are fantastic! But the process to distribute your widget to the community right now is quite unintuitive, and there isn't currently a set standard for how widgets should be packaged or shared. As such, I want to propose a potential solution for sharing widgets across the community.
Publishing widgets to NPM
NPM (Node Package Manager) is the default package manager for Node.js, acting as the world's largest software registry for JavaScript and TypeScript. Node.js is already a required item in the install process for Experience Builder developer edition, meaning that all users will already have npm available. To give a brief description of the advantages of npm packages over static zip files, or GitHub repos: npm packages offer versioned, dependency-aware distribution — meaning consumers can pin to a specific version, receive patch updates automatically, and trust that all peer dependencies are resolved correctly. Unlike a zip file buried in a blog
