@fabric-ds/elements
Advanced tools
The project uses Vite for "unbundled" local development. Start a local dev server by running the following command:
npm run dev
Changes to either the custom elements or the HTML files should hot reload.
This project uses Semantic Release to
automate package publishing when making changes to the main or next branch.
It is recommended to branch off the next branch and follow
conventional commits when making changes.
When your changes are ready for pull request, this should be opened against the next branch.
Read more in-depth about Fabric Releases here.
Please note that the version published will depend on your commit message structure. We use commitizen to help follow this structure:
npm install -g commitizen
When installed, you should be able to type cz or git cz in your terminal to commit your changes
(replacing git commit).
FAQs
Custom elements for Fabric
The npm package @fabric-ds/elements receives a total of 82 weekly downloads. As such, @fabric-ds/elements popularity was classified as not popular.
We found that @fabric-ds/elements demonstrated a not healthy version release cadence and project activity because the last version was released a year ago.Ā It has 6 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Malicious PyPI checkers validate stolen emails against TikTok and Instagram APIs, enabling targeted account attacks and dark web credential sales.
Security News
The Node.js TSC opted not to endorse a feature bounty program, citing concerns about incentives, governance, and project neutrality.
Research
Security News
A look at the top trends in how threat actors are weaponizing open source packages to deliver malware and persist across the software supply chain.