Security News
tea.xyz Spam Plagues npm and RubyGems Package Registries
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
eslint-config-fluid
Advanced tools
Readme
fluid-project eslint configuration
To use the eslint configuration provided by this module add it as a dev dependency
npm install eslint-config-fluid --save-dev
When using the default shareable configuration or the JSDoc only configuration, you'll also need to install eslint-plugin-jsdoc.
npm install eslint-plugin-jsdoc --save-dev
Next add an extends
property to your eslint configuration.
{
"extends": "eslint-config-fluid"
}
Alternatively, the "eslint-config-" prefix is assumed and can be ommited. See: Using a Shareable Config
{
"extends": "fluid"
}
The eslint-config-fluid
sharable configuration is actually a combination of the base fluid eslint configuration and
configuration for the eslint-plugin-jsdoc plugin. The latter
handling validation of jsdoc syntax; which has been depracted
from eslint. It is possible to use only one of these configurations.
To only use the Fluid setings for Eslint, add the following extends
property to your eslint configuration.
{
"extends": "fluid/fluid-config"
}
To only use the JSDoc configuration for the eslint-plugin-jsdoc
plugin, add the following extends
property to your eslint configuration.
{
"extends": "fluid/jsdoc-config"
}
When using the eslint configuration provided by this module, you may have a case where you'd like to adjust or extend the configuration. To do this, add any additional configuration to your own .eslintrc.json file, which extends the one held in this project.
In the following example, we want to add a new global for the Infusion 2.0.0 versioned namespace to our project. The
default configuration provided by the module defines a global for the generic "fluid"
namespace, so we need to extend
the configuration with an additional global, in this case "fluid_2_0_0"
.
{
"extends": "eslint-config-fluid",
"globals": {
"fluid_2_0_0": true
}
}
See the eslint user-guide for more configuration options.
See the eslint sharable configs documentation for full details.
To modify the eslint rules provided by this module, update the configuration files:
See the eslint user-guide for configuration options.
To test your changes locally, link the package globally on your system.
# run from the eslint-config-fluid directory.
# depending on your system, you may need to use sudo
npm link
Add your linked module to the package you want to test in.
# in the root directory for the package you want to test the configuration with
npm link eslint-config-fluid
Remove the links to clean up the test settings.
# run from the eslint-config-fluid directory.
# depending on your system, you may need to use sudo
npm unlink
# in the root directory for the package you tested the configuration with
npm unlink eslint-config-fluid
# run the install again to ensure that all the dependencies are properly installed
npm install
FAQs
fluid-project eslint configuration
The npm package eslint-config-fluid receives a total of 196 weekly downloads. As such, eslint-config-fluid popularity was classified as not popular.
We found that eslint-config-fluid 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
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
Security News
As cyber threats become more autonomous, AI-powered defenses are crucial for businesses to stay ahead of attackers who can exploit software vulnerabilities at scale.
Security News
UnitedHealth Group disclosed that the ransomware attack on Change Healthcare compromised protected health information for millions in the U.S., with estimated costs to the company expected to reach $1 billion.