
Security News
Crates.io Users Targeted by Phishing Emails
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.
@qooxdoo/eslint-config-qx
Advanced tools
ESLint shareable config for Qooxdoo
This depends on @qooxdoo/eslint-plugins-qx
$ npm install --save-dev @qooxdoo/eslint-config-qx
For the esnext
version you'll also need Babel's ESLint parser and plugin:
$ npm install --save-dev babel-eslint eslint-plugin-babel
This will let you use ES2016 features like async
/await
and decorators. For a full list of features see Babel's experimental features and their Learn ES2015.
package.json
Create a new file package.json
with the following contents in your project:
{
"name": "<appname>",
"description": "<appdesc>",
"author": "Your Name <your@email.com>",
"version": "0.0.1",
"license": "MIT",
"dependencies": {},
"devDependencies": {
"@qooxdoo/eslint-config-qx": "^0.0.7"
},
"engine": "node >= 4.5",
"eslintConfig": {
"extends": [
"qx"
]
},
"scripts": {
"eslint": "eslint --cache"
}
}
Replace name, description and author ofc.
package.json
Add these lines to it:
{
"devDependencies": {
"@qooxdoo/eslint-config-qx": "^0.0.7"
},
"eslintConfig": {
"extends": [
"@qooxdoo/eslint-config-qx/browser"
]
},
"scripts": {
"eslint": "eslint --cache"
}
}
Add .eslintcache
to it.
eslint
and eslint-config-qx
$ npm install
$ npm run eslint -- .
Or lint AND fix:
$ npm run eslint -- --fix .
Normaly your app has its own globals, like qxl
for Qooxdoo Contribs,
for that you need to extend @qooxdoo/eslint-config-qx/browser
with your own config.
Create a file .eslintrc-qx
:
{
"globals": {
"qxl": false
}
}
This file tells eslint to ignore qxl
but don't allow writes to it.
Now you need to tell eslint about it in package.json
:
{
"eslintConfig": {
"extends": [
"@qooxdoo/eslint-config-qx/browser"
".eslintrc-qx"
]
}
}
Thats all.
.eslintignore
ESLint has its own .eslintignore
file, when you run npm run eslint .
it will lint
all JS files found including generated ones, to exclude them you can create a
.eslintignore
and files/directories to it like in .gitignore
.
This is mine:
build/
gh-pages/
node_modules/
source/script/
source/resource/
# No need for lint
Gruntfile.js
Supports parsing ES2015, but doesn't enforce it by default.
This package also exposes qx/esnext
if you want ES2015+ rules:
{
"extends": "@qooxdoo/eslint-plugins-qx/esnext"
}
And qx/browser
if you're in the browser:
{
"extends": "@qooxdoo/eslint-config-qx/browser"
}
If you want only check for safety-errors then extend qx/safety:
{
"extends": "@qooxdoo/eslint-config-qx/safety"
}
MIT
FAQs
ESLint shareable config for Qooxdoo
We found that @qooxdoo/eslint-config-qx demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 5 open source maintainers 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
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.
Product
Socket now lets you customize pull request alert headers, helping security teams share clear guidance right in PRs to speed reviews and reduce back-and-forth.
Product
Socket's Rust support is moving to Beta: all users can scan Cargo projects and generate SBOMs, including Cargo.toml-only crates, with Rust-aware supply chain checks.