Webhint Visual Studio Code extension
User guide
- Getting Started
Api
Concepts
Configurations
Configuring webhint
Connectors
Development flow integration
Extensions
Formatters
Hints
- Avoid CSS limits
- Avoid HTTP redirects
- axe accessibility check
- Babel configuration hint set
- Compatibility of CSS, HTML and JavaScript features
- Correct `Content-Type` header
- Correct manifest extension
- Correct viewport
- Detect CSS Reflows
- Disallowed HTTP headers
- External links disown opener
- Has web app manifest
- Highest document mode
- HTTP cache
- Leading '.' in `classList.add` or `classList.remove`
- Manifest has name
- Minify JavaScript
- Modern DOCTYPE
- No `createElement` with SVG
- No `P3P` headers
- No broken links
- No byte-order mark
- No Inline CSS Styles
- No protocol-relative URLs
- No small error pages
- No vulnerable libraries
- Nu HTML test
- Optimal compression
- Optimize images
- Performance budget
- Prefixed CSS first
- scoped-svg-styles
- Specify button type
- SSL server test
- TypeScript configuration hints set
- Unneeded HTTP headers
- Use `Strict-Transport-Security` header
- Use `X-Content-Type-Options` header
- Use Apple touch icon
- Use charset `utf-8`
- Use HTTPS
- Use subresource integrity
- Valid `Set-Cookie` header
- Valid `theme-color`
- Valid manifest
- webpack configuration hints set
Parsers
Server configurations
Troubleshoot
- Api
- Concepts
- Configurations
- Configuring webhint
- Connectors
- Development flow integration
- Extensions
- Formatters
- Hints
- Parsers
- Server configurations
- Troubleshoot
Webhint Visual Studio Code extension
Use webhint
to improve your website during development.
The Webhint Visual Studio Code extension provides diagnostic data for
workspace files based on webhint
analysis.
Configuration
The extension uses the @hint/configuration-development
configuration by
default. The @hint/configuration-development
configuration activates hints
and parsers for HTML and template-making systems (JSX/TSX, Angular, and so
on), JavaScript/TypeScript, common pitfalls, and more. The
@hint/configuration-development
configuration is defined in
index.json.
For more information about what is enabled, go to package on GitHub.
To report any incorrect hints or unexpected responses, please open a new issue on GitHub.
If you want more control over what gets activated, create a local .hintrc
file
to configure webhint
.
For more information about the .hintrc
file, go to
Summary.
Contribute to the extension
To contribute to the extension, go to Contributing on GitHub.
Help
For more information about webhint
, go to webhint.io. For
more information about the output from specific hints, go to
Hints categories.