@crowdstrike/tailwind-toucan-base v5.0.0
@crowdstrike/tailwind-toucan-base
A Tailwind preset that provides the base styles for CrowdStrike's Toucan design system.
Usage
yarn add @crowdstrike/tailwind-toucan-base
#
npm install @crowdstrike/tailwind-toucan-base
#
pnpm add @crowdstrike/tailwind-toucan-baseTailwind
Note: This preset is presently only tested with Tailwind v2
// tailwind.config.js
module.exports = {
presets: [require('@crowdstrike/tailwind-toucan-base')],
extends: {
// your customizations here
}
};CSS @import
If your packager supports importing styles directly from an npm package, the Toucan styles are pre-built and can be imported at:
@import "@crowdstrike/tailwind-toucan-base";CDN Usage
Many JS CDNs scrape NPM and automatically serve and cache assets deployed to NPM.
Here as an example with JSDelivr
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@crowdstrike/tailwind-toucan-base/toucan.css">Previewing the config locally
pnpm startwhich is an alias for:
pnpm run build:preview
npx http-server ./distNote that changes to src or build scripts will require re-running pnpm start.
Previewing manual tests locally
pnpm buildthen, open the manual-test.html
firefox ./manual-test.htmlOr, along with the tailwind-preview
pnpm startand visit http://localhost:8080/manual
Importing colors and shadows from Figma
This addon provides the ability to pull our palette information directly from Figma files and store them in
themes.json which is used by the Tailwind configuration to set up our CSS.
To import the colors run:
FIGMA_TOKEN=some-key \
LIGHT_ID=fileId \
DARK_ID=fileId \
MEZZANINE_ID=fileId \
pnpm run figma:export-stylesFIGMA_TOKENhere is figma Personal Access Token.LIGHT_ID,DARK_ID, andMEZZANINE_IDarefileIds that can be obtained from the URL of the figma project containing the color tokens.
...and commit the changes to themes.json.
If you see any errors reported then you may need to ensure that the Figma file is set up correctly (and e.g. there are corresponding colors across each of the palettes).
If there are resulting changes to the output, you'll need to update the test snapshots.
That can be done via pnpm exec vitest --update
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago