Gathering detailed insights and metrics for @deskpro/apps-components-style
Gathering detailed insights and metrics for @deskpro/apps-components-style
Gathering detailed insights and metrics for @deskpro/apps-components-style
Gathering detailed insights and metrics for @deskpro/apps-components-style
npm install @deskpro/apps-components-style
Typescript
Module System
Node Version
NPM Version
JavaScript (85.96%)
CSS (13.34%)
Shell (0.69%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
90 Commits
6 Watchers
11 Branches
5 Contributors
Updated on Jan 31, 2024
Latest Version
0.12.5
Package Id
@deskpro/apps-components-style@0.12.5
Unpacked Size
192.61 kB
Size
86.88 kB
File Count
11
NPM Version
6.4.1
Node Version
8.16.0
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
CSS Styling for Deskpro Apps.
View Documentation and Examples
Goals:
Non-goals:
Summary:
npm install
npm run dev
http://localhost:3000/apps-style/
in your browsersrc/
and docs in docs/
. As you edit files, the docs site above will live reload.node
and npm
installed on your computernpm install
to initialize dependenciesTo start with, run npm run dev
to start the built-in dev server. This should open your browser at http://localhost:3000/apps-style/
with the documentation site.
As you modify CSS files in src/
and markdown documentation files in docs/
, your browser will live relaod. This makes for a really fast and smooth dev experience.
Here's an example. Say you're working on buttons:
src/components/buttons.css
and docs/components/buttons.md
http://localhost:3000/apps-style/docs/components/buttons.html
buttons.css
, update buttons.md
documentation and examples. Your browser will live-reload as you go.CSS is being post-processed with PostCSS with the postcss-preset-env which enables a bunch of proposed CSS features like variables. We use Stage 0 features.
The general idea is to stay as close to "normal CSS" as we can. i.e. we want to avoid using programming logic like loops, which is why we have avoided SASS or LESS. PostCSS offers just enough convenience (e.g. nested selectors) without going overboard.
This project is linted with stylelint and a SUIT linter plugin. Refer to the documentation if you run into issues or need to tweak the config in some way.
dp-
namespace on all components.
.dp-Button.Button--warning
.docs/
that describe and demonstrate the component and any of its modifiers.The documentation pages in docs/
serve as your "development playground" while you make changes to CSS, but by the time you finish a component, it should also serve as real documentation too.
Documentation is written in Markdown. There are two special bit of fenced HTML:
html @preview
will render the HTML code to the browser screen and show a "toggle code" button that you can click to show the source code. This is what your examples should be written in.html @render
is similar, except there is no button to show the source code. So this is an escape-hatch for (rare) cases you need to render arbitrary HTML.Most of your documentation will be written with examples in html @preview
fenced blocks. For example:
1 ```html @preview
2 <button class="dp-Button">Default</button>
3 <button class="dp-Button Button--primary">Primary</button>
4 <button class="dp-Button Button--warning">Warning</button>
5 ```
This results in three buttons being rendered to the page with "toggle code" button that will reveal that exact source code. So this is perfect for documentation to show off how to use code.
When you start a new component you'll need to create a new docs file for it:
docs/components/my-component.md
. Here's an example:1 ---
2 title: My Component
3 ---
4
5 # My Component
6
7 This is my great component.
8
9 ```html @preview
10 <div class="dp-MyComponent">
11 Here's an example!
12 </div>
13 ```
This new file maps directly to the URL http://localhost:3000/apps-style/docs/components/my-component.html
website/sidebars.json
and add it.No vulnerabilities found.
Reason
no binaries found in the repo
Reason
Found 0/15 approved changesets -- score normalized to 0
Reason
project is archived
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
license file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
188 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
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