![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
dino_ui_tools
Advanced tools
See UI library for live demos and comprehensive docs.
npm install dino_ui_tools
Then use it in your app:
import React from 'react';
import { Button } from 'dino_ui_tools/components/Button';
import 'dino_ui_tools/assets/styles/styles.scss';
// Or you can import the styles.css file
// import 'dino_ui_tools/assets/styles/styles.css';
const App = () => {
return <Button>Click me</Button>;
};
How to use mixins:
@use "dino_ui_tools/assets/styles/helpers/mixin";
.divider {
@include mixin.flexbox();
}
1. Add a new svg file in `svg-icons` folder.
2. Make sure the icon is matching with the design.
3. Make sure the svg file name is matching with pattern like this `chevron-right.svg`.
4. Run `npm run generate-svg-component` command to generate the new icon component.
1. Add a folder with the component name in `src/components/` folder.
2. Add a style file in the `assets/styles/components` fodler with the name `_componentName.scss`.
3. Import the created style file in `assets/styles/styles.scss` file using @use syntax.
4. Develop component based on the design.
5. Add `coomponentName.stories.tsx` file in src/stories folder to test created component.
6. Make sure you don't have type error and the component is matching with the design.
7. If everything is ok you can create a pull request into the master branch with correct commit message (you can read about it below).
8. The new version will be published automatically after the pull request is reviewed and merged.
This project uses Semantic Release to automate versioning and releases. It follows Semantic Versioning (semver) and determines the next version number based on commit messages.
Semantic Release automates:
1. Version number updates.
2. Release notes generation.
3. Package publishing to npm.
4. GitHub release creation.
Semantic Release uses Conventional Commits to determine release types:
`fix:` – for bug fixes (patch release)
`feat:` – for new features (minor release)
`BREAKING CHANGE:` – for breaking changes (major release)
To trigger a release:
1. Commit your changes using the conventional commit format.
2. Open a pull request and merge it into the `master` branch with the appropriate commit message.
Semantic Release will handle the rest, including publishing to npm and creating a GitHub release.
FAQs
UI library for Dino
We found that dino_ui_tools demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 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.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.