
Security News
Crates.io Users Targeted by Phishing Emails
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.
@growflow/webpack
Advanced tools
Shareable ESLint, Prettier, and TypeScript configuration to be used in Javascript/TypeScript applications to apply syntax and styling rules across GrowFlow projects.
You can easily install these packages and all of their peer dependencies with install-peerdeps:
npx install-peerdeps --dev @growflow/eslint-config
npx install-peerdeps --dev @growflow/prettier-config
npx install-peerdeps --dev @growflow/tsconfig
You can then create a .eslintrc.js
file with content similar to the following:
module.exports = {
extends: ['@growflow'],
parserOptions: {
project: 'tsconfig.json',
},
};
Add a prettier
field to your package.json
to use the shared prettier config:
{
"name": "my-cool-app",
"version": "1.0.0",
"prettier": "@growflow/prettier-config"
}
Add a tsconfig.json
to the root of your project with contents similar to the folowing:
{
"extends": "@growflow/tsconfig",
"include": ["src", "test"]
}
You should be able to use your favorite editor's (*cough* VS Code) ESLint and/or Prettier plugin to easily format your code on save or with the Format command.
Clone this repo and run yarn
from the repository's root to install dependencies.
package.json
to your new folder and tweak the values.package.json
file, add the new folder to the workspaces
property.In order for a local copy of an external frontend to use a local copy of one of these packages (e.g. @growflow/eslint-config), we have to "link" them locally.
Normally we would use yarn link
to achieve this, but there are known issues that cause errors with React.
The best alternative solution is to use the utility yalc.
The below examples use @growflow/eslint-config
and wholesale-frontend
as an example.
First, make sure to install yalc
globally on your machine:
yarn global add yalc
or
npm i yalc -g
Then,
eslint
folder, run yalc publish
.wholesale-frontend
, inside the root package.json
file, under the workspaces
property, add a new entry .yalc/@*/*
(this only needs to be done one time)wholesale-frontend
, run yalc link "@growflow/eslint-config"
and yarn install
yarn clean
and re-run yarn install
yalc remove --all
. This prevents yarn.lock
from incorrectly thinking there is a local copy of @growflow/eslint-config
instead of pulling from npm.This repository uses lerna to manage its packages.
Don't manage version numbers within package.json
by hand. Instead, after you have made and pushed your changes, run:
yarn release
which will guide you in bumping the version and confirm what packages are about to be published. It will also auto-create tags. You can then create a release in GitHub on the generated tag to create a changelog.
FAQs
Shareable Webpack configuration used in GrowFlow projects
We found that @growflow/webpack demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 15 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
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.
Product
Socket now lets you customize pull request alert headers, helping security teams share clear guidance right in PRs to speed reviews and reduce back-and-forth.
Product
Socket's Rust support is moving to Beta: all users can scan Cargo projects and generate SBOMs, including Cargo.toml-only crates, with Rust-aware supply chain checks.