Security News
pnpm 10.0.0 Blocks Lifecycle Scripts by Default
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
anvil.csslint
Advanced tools
This plugin requires anvil.js version 0.8.* or greater.
anvil install anvil.csslint
After you have installed the plugin you first need to reference the plugin inside the dependencies
key of your build.json
.
{
"source": "src",
"spec": "spec",
"output": [ "build" ],
"dependencies" : [ "anvil.csslint" ],
"anvil.csslint": {
// Required settings here...
}
}
Then you will need to choose one of the following senarios in order for the plugin to know which files to lint.
Let's say that you had 5 CSS files in your src
folder and you wanted all of them to be linted when you build your project. The following "all": true
setting will tell anvil.csslint
that you want everything to be linted.
{
"source": "src",
"spec": "spec",
"output": [ "build" ],
"dependencies" : [ "anvil.csslint" ],
"anvil.csslint": {
"all": true
}
}
If you had 5 CSS files in your src
folder and you only wanted a specific subset of those to be linted, then you could use the include
setting and provide a list of files you want to include in the linting process.
{
"source": "src",
"spec": "spec",
"output": [ "build" ],
"dependencies" : [ "anvil.csslint" ],
"anvil.csslint": {
"include": [ "main.css" ]
}
}
If you had 5 CSS files in your src
folder and you wanted most of them to be linted, but to ignore a couple of items, then you could use the exclude
setting and provide a list of files you want to exclude in the linting process.
{
"source": "src",
"spec": "spec",
"output": [ "build" ],
"dependencies" : [ "anvil.csslint" ],
"anvil.csslint": {
"exclude": [ "util.css" ]
}
}
By default if there are any errors that CSSLint returns then the build process will be aborted. You can override this option by providing setting the breakBuild
to false
.
{
"source": "src",
"spec": "spec",
"output": [ "build" ],
"dependencies" : [ "anvil.csslint" ],
"anvil.csslint": {
"all": true,
"breakBuild": false
}
}
Sometimes there are CSSLint errors that for one reason or another you want ignored by the build process. To do that you can provide an ignore
option with a list of all the errors that you feel are acceptable for your project. You list the line
, character
, and reason
(contains) of each error you'd like to ignore. You can provide a combination of these options for more or less flexibility.
{
"source": "src",
"spec": "spec",
"output": [ "build" ],
"dependencies" : [ "anvil.csslint" ],
"anvil.csslint": {
"all": true,
"ignore": [
{ "line": 81, "character": 26, "reason": "'someVariable' is already defined." },
... other options ...
]
}
}
The following option ignores message for line 1 and col 15
{ "line": 1, "col": 15, "message": "Expected COLON at line 1, col 15." }
The following option ignores any error on line 81 and col 12
{ "line": 81, "col": 12 }
The following option ignores message anywhere on line 81
{ "line": 81, "message": "Don't use IDs in selectors." }
The following option ignores any errors on line 81
{ "line": 81 }
The following option ignores any errors matching message anywhere in the file
{ "message": "Don't use adjoining classes." }
You can always provide custom CSSLint and global comments to the top of each of your CSS file to tweak it's lint ruleset
settings, but that can be redundant and a nuisance. So, you can provide these common settings in your 'anvil.csslint' settings to be used during the linting process. For more information about these seeting check the official wiki.
{
"source": "src",
"spec": "spec",
"output": [ "build" ],
"dependencies" : [ "anvil.csslint" ],
"anvil.csslint": {
"all": true,
"ruleset": {
"important":1,
"adjoining-classes":1,
"known-properties":1,
"box-sizing":1,
"box-model":1,
"outline-none":1,
"duplicate-background-images":1,
"compatible-vendor-prefixes":1,
"display-property-grouping":1,
"qualified-headings":1,
"fallback-colors":1,
"duplicate-properties":1,
"empty-rules":1,
"errors":1,
"shorthand":1,
"ids":1,
"gradients":1,
"font-sizes":1,
"font-faces":1,
"floats":1,
"underscore-property-hack":1,
"overqualified-elements":1,
"import":1,
"regex-selectors":1,
"rules-count":1,
"star-property-hack":1,
"text-indent":1,
"unique-headings":1,
"universal-selector":1,
"unqualified-attributes":1,
"vendor-prefix":1,
"zero-units":1
}
}
}
anvil uninstall anvil.csslint
FAQs
CSSLint plugin for anvil.js
The npm package anvil.csslint receives a total of 1 weekly downloads. As such, anvil.csslint popularity was classified as not popular.
We found that anvil.csslint 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
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
Product
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.
Research
Security News
Socket researchers have discovered multiple malicious npm packages targeting Solana private keys, abusing Gmail to exfiltrate the data and drain Solana wallets.