
Security News
Another Round of TEA Protocol Spam Floods npm, But It’s Not a Worm
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.
@wpackio/eslint-config
Advanced tools
@wpackio/eslint-configShared ESLint configuration for all @wpackio packages and more. It has shared
config for both JavaScript and TypeScript projects.
Note that this doesn't come installed with @wpackio/scripts. If you wish to
take advantage of this config, then install and use on your own.
If using yarn
yarn add --dev @wpackio/eslint-config eslint prettier
or with npm
npm i -D @wpackio/eslint-config eslint prettier
Using it with JavaScript project is very simple. Create a .eslintrc.js file in the root of your project and put the code.
module.exports = {
extends: '@wpackio',
};
Using with typescript requires a little more effort. In the same .eslintrc.js
file, put
module.exports = {
extends: ['@wpackio/eslint-config/ts'],
parserOptions: {
project: './tsconfig.json',
tsconfigRootDir: __dirname,
},
settings: {
'import/resolver': {
typescript: {
directory: __dirname,
},
},
},
};
Putting __dirname in parserOptions.tsconfigRootDir and ['import/resolver'].typescript
is necessary because of this issue.
For both the cases you can also extend upon the rules.
Create a prettier.config.js file in the root of your project and put the code.
module.exports = require('@wpackio/eslint-config/prettier.config');
Now you are ready to go.
Install the eslint
plugin for VSCode. Enable autoFormat for javascript and javascriptreact files.
{
"eslint.autoFixOnSave": true,
"[javascript]": {
"editor.formatOnSave": false
},
"[javascriptreact]": {
"editor.formatOnSave": false
}
}
If you are using for typescript files, the following additional settings are needed.
{
"eslint.validate": [
"javascript",
"javascriptreact",
{ "language": "typescript", "autoFix": true },
{ "language": "typescriptreact", "autoFix": true }
]
}
This package has the same npm scripts as this monorepo. These should be run
using lerna run <script>. More information can be found under CONTRIBUTION.md.
build: Use babel to build for nodejs 8.6+. Files inside src are compiled and put under lib. All type definitions are stripped and individual type declaration files are created.prepare: Run build after yarn and before publish.lint: Lint all files using tslint.test: Run tests on files using jest.FAQs
Shared ESLint config for all @wpackio packages.
The npm package @wpackio/eslint-config receives a total of 4 weekly downloads. As such, @wpackio/eslint-config popularity was classified as not popular.
We found that @wpackio/eslint-config 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
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.

Security News
PyPI adds Trusted Publishing support for GitLab Self-Managed as adoption reaches 25% of uploads

Research
/Security News
A malicious Chrome extension posing as an Ethereum wallet steals seed phrases by encoding them into Sui transactions, enabling full wallet takeover.