-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Something else to consider is applying linting and formatting before every git commit. A package like Lint-staged only lints and formats on staged items, ensuring all pushed code follows the standards in the repo. This allows developers to have their own formatting preferences when developing, while the code homogenizes on push. Linting pre-commit also avoids strict rules like no-console or no-unused-vars restricting a developer when writing code, when it should only apply in production. Imagine not being able to console log anything during development!
I’m sure you know Husky; it’s on basically every project. Pre-commit hooks are important for the development process of any codebase and ensure code meets a standard before being pushed up. This is the perfect time to perform certain actions, like running unit and integration tests, to make sure your latest code changes don't break anything. It’s also a good time for running linting and formatting to match the standards of the repo. If Husky isn’t there, add it!
Adding Mock Service Worker can also be a great addition not only for testing, but for a proof-of-concept or MVP with a backend that is not quite ready. MSW intercepts fetch requests and allows insertion of mock sample data, allowing a complete imitation of API capabilities. With this, all tests and even the prototype of your application can be presented with full functionality without needing to hit a backend API.
Not only do tests ensure a robust codebase, but writing them allows the developer to get familiar with existing components and their business logic. Add some simple Jest and React Testing Library tests to check that UI components are rendering properly and user actions are firing correctly.
A lot of proof-of-concept and MVP projects start out with a number of libraries meant to be temporary. Maybe the app was using Chakra UI for its modal and custom buttons, while the rest of the imported library is just dead weight. Perhaps developers have been spending more time adjusting Semantic UI’s styling to match the designs than it’s worth.