Community
JOPS lives on GitHub at uidb-dev/jops-core. That is where releases are published and where you can reach the maintainer.
Issues, not pull requests
Section titled “Issues, not pull requests”The repository accepts issues, not pull requests. Pull requests from outside the project are closed automatically. If you have a change in mind, describe it in an issue (a bug report or a feature request), and it will be discussed there.
A good bug report includes the JOPS version, whether you load it from npm or the CDN, the browser, and the smallest code that shows the problem.
How JOPS is distributed
Section titled “How JOPS is distributed”JOPS is distributed as a single minified ES module (lib/jops-core.min.js) together with full TypeScript declarations (lib/jops-core.d.ts), plus the JopsApp React component for Next.js (lib/nextjs/, imported as jops-core/nextjs). The source repository is private.
This is a deliberate choice. JOPS is maintained by one developer at UIDB, and keeping the code base in one pair of hands keeps it small, consistent and fast to change.
What that means for you:
- Free to use. JOPS is MIT-licensed. Use it in personal, commercial and client projects.
- The API is the contract. Every public class, method and lifecycle hook is documented on this site and typed in
jops-core.d.ts, so your editor gives you autocomplete and inline docs. - Readable stack traces. The build keeps class and function names, so errors point to
View.loadLayout, note.t. - Backwards compatible within a major version. Pin
jops-core@1if you want to control major upgrades.
License
Section titled “License”JOPS is released under the MIT License, © UIDB.