Gathering detailed insights and metrics for @contentful/f36-datetime
Gathering detailed insights and metrics for @contentful/f36-datetime
Gathering detailed insights and metrics for @contentful/f36-datetime
Gathering detailed insights and metrics for @contentful/f36-datetime
npm install @contentful/f36-datetime
@contentful/f36-components@4.74.3
Published on 27 Nov 2024
@contentful/f36-core@4.74.3
Published on 27 Nov 2024
@contentful/f36-typography@4.74.3
Published on 27 Nov 2024
@contentful/f36-tooltip@4.74.3
Published on 27 Nov 2024
@contentful/f36-text-link@4.74.3
Published on 27 Nov 2024
@contentful/f36-tabs@4.74.3
Published on 27 Nov 2024
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
335 Stars
3,696 Commits
81 Forks
61 Watching
33 Branches
274 Contributors
Updated on 28 Nov 2024
TypeScript (84.3%)
JavaScript (11.43%)
MDX (3.55%)
CSS (0.57%)
Handlebars (0.15%)
Cumulative downloads
Total Downloads
Last day
-26.6%
4,739
Compared to previous day
Last week
1.1%
30,561
Compared to previous week
Last month
30.9%
136,917
Compared to previous month
Last year
-36.1%
1,235,436
Compared to previous year
Forma 36 is an open-source design system by Contentful created with the intent to reduce the overhead of creating UI by providing tools and guidance for digital teams building and extending Contentful products
We use Plop to create scripts that help you to scaffold new packages. In the root of the repo, you can run npm run-script generate
. Then follow the steps in the CLI. Plop will generate the relevant files and add the relevant imports and exports to the main src/index.ts
file required to make the component available when publishing the library. Read more about contribution to Forma 36.
For local development, in the root of the repo run npm i
to install all dependencies and then npm run-script build
to build all packages. Now follow the instructions of the specific package you’re working on.
You will find each package’s instructions in their README files, check the Packages section for a list of all packages.
In case you are having problems to install the dependencies, try using NVM to get the same node version we use by running
nvm use
in the root of the repo
We use storybook with our react component library to develop components. You can start it from the root of the repo, just run npm run-script storybook
after building.
Use npm run-script commit
. This uses the Commitzen CLI to create a conventional commit message based on your changes. CI is setup to release all new commits on the main branch that contains a new changeset.
Read more about changeset here
You can test changes to a package of this monorepo in your own project locally by taking the following steps:
npm run-script build
in the desired package's directory to ensure your latest changes have been builtnpm link
in the desired package's directorynpm link NAME_OF_PACKAGE
to link to the local version of the package (e.g. npm link @contentful/f36-components
)We appreciate any help on our repositories. For more details about how to contribute to a package, see the README of the corresponding package.
You can reach out to us using the Contentful Community Discord.
Create an issue using one of the templates . Make sure to remove any credential from your code before sharing it.
This repository is published under the MIT license.
We want to provide a safe, inclusive, welcoming, and harassment-free space and experience for all participants, regardless of gender identity and expression, sexual orientation, disability, physical appearance, socioeconomic status, body size, ethnicity, nationality, level of experience, age, religion (or lack thereof), or other identity markers.
Read our full Code of Conduct.
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!
No vulnerabilities found.
Reason
30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
security policy file detected
Details
Reason
no binaries found in the repo
Reason
Found 13/26 approved changesets -- score normalized to 5
Reason
dependency not pinned by hash detected -- score normalized to 2
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
project is not fuzzed
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
29 existing vulnerabilities detected
Details
Score
Last Scanned on 2024-11-25
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More