Every RShift Sites project can use npm packages, ready-made JavaScript libraries for features like drag-and-drop, charts, animations, and date handling. You do not install anything yourself. Name the package in the project chat, or just describe the feature you want, and RShift Sites installs the package and wires it into your app.
Ask for a package in the project chat
Say you want to arrange tasks in Kanban boards, like in popular project management tools. You can prompt RShift Sites to build drag-and-drop from scratch, but a dedicated package gets you robust behavior faster. For example, @hello-pangea/dnd provides drag-and-drop functionality that supports adding cards, moving them between columns, and reordering them.
Use the @hello-pangea/dnd npm package to add drag-and-drop functionality to my Kanban board app. Ensure users can add new cards, move them within columns, and reorder them.RShift Sites installs the package and integrates it into your project. Depending on your other requirements, the result might look like this.
You can also describe the outcome without naming a package (“add drag-and-drop to my board”). For well-established problems like this, RShift Sites prefers proven libraries over hand-rolled code and picks a suitable package for you.
Choose packages carefully
RShift Sites installs any public npm package you ask for, but it cannot guarantee the quality, security, or reliability of third-party code. Test features built on a package thoroughly before you rely on them.
Before integrating a package, check:
- Downloads: A high download count on the package’s npm page indicates the package is widely used and trusted by the community.
- Maintenance: Look at the package’s repository. Frequent commits, recent releases, and responsiveness to issues are good signs. A package that has not been updated in years is more likely to break with current dependencies and security practices.
- Community feedback: Read issues and discussions on the package’s GitHub repository, and search developer forums for reports of problems.
Also keep in mind that RShift Sites apps run in the browser with a serverless backend. Packages built for other environments, such as Electron (desktop apps) or Capacitor native plugins (mobile apps), install without errors but do not work in your published app.
FAQ
Do I need to install packages myself?
No. Ask for the package or the feature in the project chat and RShift Sites adds it to your project’s dependencies. There is no terminal step or manual package.json editing.
How do I update or remove a package?
Ask in the project chat. Prompts like “remove the moment package” or “update recharts to the latest version” work the same way as installing.
Can I use private or internal packages?
Yes, on the Enterprise plan. Set up a managed registry for your workspace to publish internal packages and install them in any workspace project.
What is the bun.lock file in my project’s code?
bun.lock (or bun.lockb) belongs to Bun, the tool RShift Sites uses to install packages. It records the exact version of every package in your project so your app builds the same way everywhere. You can see it in your project’s code files, and in your repository if you sync the project to a Git repository. Leave the file in place. If you run the project outside RShift Sites, install dependencies with Bun so the versions stay in sync.