Package Exports
- @open-wc/eslint-config
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@open-wc/eslint-config) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Linting ESLint
Use ESLint to lint your es6 code.
Part of Open Web Components: guides, tools and libraries for modern web development and web components
Setup
npm init @open-wc
# Upgrade > Linting::: tip This is part of the default open-wc recommendation :::
Manual
- Install
@open-wc/eslint-confignpm add --save-dev @open-wc/eslint-config
- Adjust your package.json with the following
{ "scripts": { "lint:eslint": "eslint --ext .js,.html . --ignore-path .gitignore", "format:eslint": "eslint --ext .js,.html . --fix --ignore-path .gitignore" }, "eslintConfig": { "extends": [ "@open-wc/eslint-config" ] } }
What you get
This will install @open-wc/eslint-config, a config based on airbnb but allows for some specialities needed for Web Components.
- Apply linting to js and html files
- Apply linting for best practices
- Allow dynamic module imports
- Allow imports in test/demos from devDependencies
- Allow underscore dangle
- Do not prefer default exports
- Do not prefer no file extension
Usage
Run:
npm run lint:eslintto check if any file is not correctly formattednpm run format:eslintto auto format your files