![Introducing Enhanced Alert Actions and Triage Functionality](https://cdn.sanity.io/images/cgdhsj6q/production/fe71306d515f85de6139b46745ea7180362324f0-2530x946.png?w=800&fit=max&auto=format)
Product
Introducing Enhanced Alert Actions and Triage Functionality
Socket now supports four distinct alert actions instead of the previous two, and alert triaging allows users to override the actions taken for all individual alerts.
@holaluz/npm-scripts
Advanced tools
Readme
npm-scripts
This package contains basic npm
scripts configs for Holaluz' front-end projects.
npm install --save-dev @holaluz/npm-scripts
...and then import/extend each config file with the ones from this library:
// babel.config.js
const babelConfig = require('@holaluz/npm-scripts').babel
module.exports = babelConfig
// .eslintrc.js
const eslintConfig = require('@holaluz/npm-scripts').eslint
module.exports = eslintConfig
// prettier.config.js
const prettierConfig = require('@holaluz/npm-scripts').prettier
module.exports = prettierConfig
// stylelint.config.js
const stylelintConfig = require('@holaluz/npm-scripts').stylelint
module.exports = stylelintConfig
// postcss.config.js
const postcssConfig = require('@holaluz/npm-scripts').postcss
module.exports = postcssConfig
// lint-staged.config.js
const lintStagedConfig = require('@holaluz/npm-scripts').lintStaged
module.exports = lintStagedConfig
// simple-git-hooks.js
const simpleGitHooks = require('@holaluz/npm-scripts').simpleGitHooks
module.exports = simpleGitHooks
You can find a check-node
script which will be triggered every time this package is installed because it resides in the preinstall
npm script. Thus displaying on the terminal if the node version requirement is not meet.
# Example of the shown log when the node versions do not match
> @holaluz/npm-scripts
> node check-node.js
Version mismatch!
You must use Node version 16 or greater to run the scripts within this repo.
Version used: v14
This config should give you autoformatting on save:
{
"[javascript]": {
"editor.formatOnSave": true,
"editor.defaultFormatter": "esbenp.prettier-vscode",
},
"[css]": {
"editor.formatOnSave": true,
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"[postcss]": {
"editor.formatOnSave": true,
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"[vue]": {
"editor.formatOnSave": true,
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"vetur.format.defaultFormatter.html": "js-beautify-html",
"vetur.validation.template": false
}
npm-scripts
uses Semantic Release to handle the release pipeline.
Triggering a new release will create the associated Git tag, the GitHub release entry, and publish a new version on npm.
In order to trigger a new version, make sure you add the appropriate prefix and message to the squashed commit. It is based on the Angular Commit Message Conventions. In short:
# Creates a patch release (v1.0.0 -> v1.0.1)
> fix: commit message
# Creates a feature release (v1.0.0 -> v1.1.0)
> feat: commit message
# Creates a breaking release (v1.0.0 -> v2.0.0)
> fix: commit message
>
> BREAKING CHANGE: explain the breaking change # "BREAKING CHANGE:" is what triggers the breaking release
There's no need to overcomplicate things here. Keep it simple: fix
, feat
,
and chore
(plus BREAKING CHANGE
) should be enough for now.
First of all, ask yourself: Does this rule really need to be local to your project? Or should I create a PR to this repo, so that it becomes available to everyone?
If the answer is "yes, it needs to be local to my project", then you can extend any config by merging the exported object with your custom config:
const merge = require('lodash.merge')
const eslintConfig = require('@holaluz/npm-scripts').eslint
module.exports = merge(eslintConfig, {
rules: {'your-rule': 'error'}
})
FAQs
[![npm](https://img.shields.io/npm/v/@holaluz/npm-scripts.svg)](https://img.shields.io/npm/v/@holaluz/npm-scripts.svg)
The npm package @holaluz/npm-scripts receives a total of 23 weekly downloads. As such, @holaluz/npm-scripts popularity was classified as not popular.
We found that @holaluz/npm-scripts demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 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.
Product
Socket now supports four distinct alert actions instead of the previous two, and alert triaging allows users to override the actions taken for all individual alerts.
Security News
Polyfill.io has been serving malware for months via its CDN, after the project's open source maintainer sold the service to a company based in China.
Security News
OpenSSF is warning open source maintainers to stay vigilant against reputation farming on GitHub, where users artificially inflate their status by manipulating interactions on closed issues and PRs.