![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
@basis-theory/eslint-config
Advanced tools
Standardized Basis Theory ESLint and Prettier configurations.
yarn add @basis-theory/eslint-config -D
Add it to extends
property of your ESLint config file (i.e. .eslintrc.js
):
module.exports = {
extends: '@basis-theory',
rules: {
// disable/enable any rules
},
};
Instead of extending the root ruleset, point to the exported Typescript flavor:
module.exports = {
extends: '@basis-theory/eslint-config/typescript',
rules: {
// disable/enable any rules
},
};
Instead of extending the root ruleset, point to the exported Next.js (Typescript) flavor:
module.exports = {
extends: '@basis-theory/eslint-config/next',
rules: {
// disable/enable any rules
},
};
Since both eslint-config-get-off-my-lawn
and eslint-config-next
use same plugins with different versions, which leads to ESLint throwing the error:
ESLint couldn't determine the plugin "{pluginName}" uniquely.
So get over that, you must add Yarn resolutions field to your package.json
:
{
"resolutions": {
"eslint-plugin-import": "2.24.2",
"eslint-plugin-react": "7.25.1"
}
}
Note: if you are using NPM, it is worth looking into (npm-force-resolutions)[https://www.npmjs.com/package/npm-force-resolutions] as an alternative to Yarn's deterministic dependency resolution.
To use only the exported config in your project, you may set the prettier
prop to your package.json
:
{
"prettier": "@basis-theory/eslint-config/prettier"
}
Or, if you want to expand on top it, create a .prettierrc.js
file with following content:
module.exports = {
...require('@basis-theory/eslint-config/prettier'),
// add your configuration here
};
@typescript-eslint/explicit-module-boundary-types
and/or @typescript-eslint/explicit-module-boundary-types
for a React component, add return type JSX.Element
as follows:
Before:
export const MyComponent = ({}: Props) => {};
After:
export const MyComponent = ({}: Props): JSX.Element => {};
FAQs
Basis Theory ESLint config
The npm package @basis-theory/eslint-config receives a total of 36 weekly downloads. As such, @basis-theory/eslint-config popularity was classified as not popular.
We found that @basis-theory/eslint-config demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 10 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
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.