
Security News
Django Joins curl in Pushing Back on AI Slop Security Reports
Django has updated its security policies to reject AI-generated vulnerability reports that include fabricated or unverifiable content.
eslint-plugin-excalibur
Advanced tools
A [typescript-eslint](https://typescript-eslint.io/getting-started) plugin for [Excalibur](https://excaliburjs.com/).
A typescript-eslint plugin for Excalibur.
typescript-eslint
is required and it only runs on Typescript files. This is so that the rules can be aware
of types in order to support some of these rules. This also means that it will take as much time to lint as it
will to compile your Typescript files. If you have ideas for how to improve this, please create an issue or PR.
First, setup eslint and typescript-eslint if you haven't already:
# eslint 9.0 is not yet supported by typescript-eslint
npm install --save-dev @typescript-eslint/parser @typescript-eslint/eslint-plugin eslint@8 typescript
Install the plugin:
npm install eslint-plugin-excalibur --save-dev
Create an eslint.config.js
file:
// @ts-check
import eslint from '@eslint/js'
import excalibur from 'eslint-plugin-excalibur'
import tseslint from 'typescript-eslint'
export default tseslint.config(
eslint.configs.recommended,
...tseslint.configs.recommended,
excalibur.configs.recommended,
)
If you are using the .eslintrc.js
config format, first read the typescript-eslint docs for setting up with legacy config.
Once you have that setup your .eslintrc.js
file should look something like this:
/* eslint-env node */
module.exports = {
extends: [
'eslint:recommended',
'plugin:@typescript-eslint/recommended',
'plugin:excalibur/recommended-legacy',
],
parser: '@typescript-eslint/parser',
parserOptions: {
project: true,
},
plugins: ['@typescript-eslint', 'excalibur'],
root: true,
}
(TODO)
For now, a list of rules can be found in the rules folder
If you get an error that looks like this
ESLint was configured to run on `<tsconfigRootDir>/something.ts` using `parserOptions.project`: /path/to/tsconfig.json
This is because a file was passed through to eslint that is not part of includes
in your tsconfig.json
. To fix this, either add the file to your includes
in tsconfig.json
or adjust the eslint config like so:
export default tseslint.config(
eslint.configs.recommended,
...tseslint.configs.recommended
{
...excalibur.configs.recommended,
// e.g. only include your src files
files: ['src/**/*.ts']
}
)
See typescript-eslint documentation for more information.
FAQs
A [typescript-eslint](https://typescript-eslint.io/getting-started) plugin for [Excalibur](https://excaliburjs.com/).
The npm package eslint-plugin-excalibur receives a total of 0 weekly downloads. As such, eslint-plugin-excalibur popularity was classified as not popular.
We found that eslint-plugin-excalibur 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
Django has updated its security policies to reject AI-generated vulnerability reports that include fabricated or unverifiable content.
Security News
ECMAScript 2025 introduces Iterator Helpers, Set methods, JSON modules, and more in its latest spec update approved by Ecma in June 2025.
Security News
A new Node.js homepage button linking to paid support for EOL versions has sparked a heated discussion among contributors and the wider community.