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.
@iopipe/scripts
Advanced tools
Readme
Scripts for IOpipe projects
This module is distributed via [npm][npm] which is bundled with [node][node] and
should be installed as one of your project's devDependencies
:
yarn add @iopipe/scripts --dev
This is a CLI and exposes a bin called iopipe-scripts.
This project actually dogfoods itself. If you look in the package.json, you'll find scripts with node src {scriptName}. This serves as an example of some of the things you can do with iopipe-scripts.
A great example of this package in use can be found at the IOpipe event-info plugin repo.
You'll see that this repo uses scripts for linting, building, testing, and releasing. You'll also find the current recommended usage for eslint, until this eslint issue is resolved.
@iopipe/scripts
allows you to specify your own
configuration for things and have that plug directly into the way things work
with @iopipe/scripts
. There are various ways that it works, but basically if you
want to have your own config for something, just add the configuration and
@iopipe/scripts
will use that instead of it's own internal config. In addition,
@iopipe/scripts
exposes its configuration so you can use it and override only
the parts of the config you need to.
This can be a very helpful way to make editor integration work for tools like ESLint which require project-based ESLint configuration to be present to work.
So, if we were to do this for ESLint, you could create an .eslintrc
with the
contents of:
{"extends": "./node_modules/iopipe-scripts/eslint.js"}
Note: for now, you'll have to include an
.eslintignore
in your project until this eslint issue is resolved.
Or, for babel
, a .babelrc
with:
{"presets": ["./node_modules/@iopipe/scripts/babel"]}
Or, for jest
:
const { jest: jestConfig } = require('iopipe-scripts/config');
module.exports = Object.assign(jestConfig, {
// your overrides here
});
Note:
iopipe-scripts
intentionally does not merge things for you when you start configuring things to make it less magical and more straightforward. Extending can take place on your terms. I think this is actually a great way to do this.
Thanks to Kent C. Dodds and contributors for the base repository. https://github.com/kentcdodds/kcd-scripts
FAQs
CLI for common scripts for IOpipe projects
The npm package @iopipe/scripts receives a total of 0 weekly downloads. As such, @iopipe/scripts popularity was classified as not popular.
We found that @iopipe/scripts demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 7 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.