Security News
Opengrep Emerges as Open Source Alternative Amid Semgrep Licensing Controversy
Opengrep forks Semgrep to preserve open source SAST in response to controversial licensing changes.
blueprint-sass-compile
Advanced tools
a handy little package to compile blueprint.scss from source
yarn install --dev blueprint-sass-compile
package.json
{
"scripts": {
"build:css": "blueprint-sass-compile <path>",
"watch:css": "blueprint-sass-compile <path> --watch",
}
}
_blueprint_variables.scss
Make a file to hold all your Blueprint variable overrides. Be sure to import this first thing in your main Sass file.
What variables are available? See below for links to source code, the ultimate source of truth.
@import '~@blueprintjs/core/lib/scss/variables';
$g: 4px;
//
// Blueprint public vars
//
$pt-grid-size: $g * 2;
$pt-border-radius: $g;
$pt-font-size: $g * 3;
$pt-font-size-large: $pt-font-size + 1px;
$pt-font-size-small: $pt-font-size - 1px;
$pt-line-height: 4 / 3;
//
// Blueprint component vars
//
$card-padding: $g * 3;
$menu-item-border-radius: $pt-border-radius;
$menu-item-line-height: $pt-grid-size * 2;
vendor.scss
In your root Sass file, import your overrides file before importing Blueprint source files. Then import all packages from src/
. This will produce a single vendor.css
file that contains all the compiled Blueprint styles in one file, from all four libraries below.
For performance reasons, it can be nice to split your external stylesheets to a separate
vendor.scss
because these will likely change much less frequently than your application styles.
// import your overrides first
@import 'blueprint_variables';
// then each blueprint package from `/src/` NOT `/lib/css/`
@import '~@blueprintjs/core/src/blueprint';
@import '~@blueprintjs/datetime/src/blueprint-datetime';
@import '~@blueprintjs/select/src/blueprint-select';
@import '~@blueprintjs/table/src/table';
> yarn build:css
yarn run v1.22.4
$ blueprint-sass-compile src/styles
Rendering Complete, saving .css file...
Wrote CSS to /src/styles/application.css
Wrote Source Map to /src/styles/application.css.map
GET https://raw.githubusercontent.com/palantir/blueprint/develop/resources/icons/16px/chevron-right.svg
GET https://raw.githubusercontent.com/palantir/blueprint/develop/resources/icons/16px/more.svg
GET https://raw.githubusercontent.com/palantir/blueprint/develop/resources/icons/16px/small-tick.svg
GET https://raw.githubusercontent.com/palantir/blueprint/develop/resources/icons/16px/small-minus.svg
Rendering Complete, saving .css file...
Wrote CSS to /src/styles/vendor.css
Wrote Source Map to /src/styles/vendor.css.map
Wrote 2 CSS files to /src/styles
✨ Done in 2.82s.
$variables
$pt-variables
: https://github.com/palantir/blueprint/blob/develop/packages/core/src/common/_variables.scss$blue3
, etc: https://github.com/palantir/blueprint/blob/develop/packages/core/src/common/_colors.scss$pt-intent-primary
, etc: https://github.com/palantir/blueprint/blob/develop/packages/core/src/common/_color-aliases.scss$pt-*
but still editable this way) must be looked up in component source code. They are typically defined in a component's main or _common.scss
file: https://github.com/search?l=&q=repo%3Apalantir%2Fblueprint+filename%3A_common.scss&type=CodeFAQs
compile blueprint.scss from source
The npm package blueprint-sass-compile receives a total of 3 weekly downloads. As such, blueprint-sass-compile popularity was classified as not popular.
We found that blueprint-sass-compile demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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
Opengrep forks Semgrep to preserve open source SAST in response to controversial licensing changes.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.