
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
parallax-common-config
Advanced tools
This is a module with all parallax-common-config configurations for team-parallax.
This is a module with all parallax-common-config configurations for team-parallax.
This is a module with opinionated configurations you might find useful. This is used internally at team-parallax.
yarn add -D parallax-common-config
Additional dependencies are required for eslint, webpack to run smoothly:
yarn add -D @typescript-eslint/eslint-plugin @typescript-eslint/parser autoprefixer awesome-typescript-loader cache-loader css-loader css-modules-typescript-loader eslint-config-react-app eslint-loader eslint-plugin-filenames eslint-plugin-sort-keys-fix eslint-plugin-import-alias eslint-plugin-jsdoc eslint-plugin-react eslint-plugin-sort-imports-es6-autofix eslint-plugin-unused-imports extract-css-chunks-webpack-plugin file-loader html-webpack-plugin style-loader svg-inline-loader typescript typescript-eslint-parser typings-for-css-modules-loader url-loader webpack-merge eslint-plugin-import
Create a symlink to use our .editorconfig
ln -s node_modules/parallax-common-config/.editorconfig .editorconfig
Create a symlink to use our .gitlab-ci.common.yml
ln -s node_modules/parallax-common-config/.gitlab-ci.common.yml .gitlab-ci.common.yml
Create a symlink to use our .editorconfig
ln -s node_modules/parallax-common-config/.browserlistrc .browserlistrc
Add this to your .eslintrc
{
"extends": [
"./node_modules/parallax-common-config/.eslintrc",
"./node_modules/parallax-common-config/.eslintrc.react",
"./node_modules/parallax-common-config/.eslintrc.typescript"
]
}
Note that there are also .eslintrc.prod
files which return errors instead of warnings. This is useful for CI
pipelines - use them like so
{
"extends": [
"./node_modules/parallax-common-config/.eslintrc",
"./node_modules/parallax-common-config/.eslintrc.react",
"./node_modules/parallax-common-config/.eslintrc.prod",
"./node_modules/parallax-common-config/.eslintrc.react.prod",
"./node_modules/parallax-common-config/.eslintrc.typescript" // TODO: create a prod-version of this one
]
}
{
"extends": "./node_modules/parallax-common-config/tsconfig.react"
}
We utilize webpack-merge
in order to modularize our webpack configurations.
const webpack = require("webpack");
const merge = require("webpack-merge");
const path = require("path");
const webpackDev = require("./node_modules/parallax-common-config/webpack.config.dev");
const webpackProd = require("./node_modules/parallax-common-config/webpack.config.prod");
const webpackCommon = require("./node_modules/parallax-common-config/webpack.config.common");
const webpackReact = require("./node_modules/parallax-common-config/webpack.config.react");
module.exports = (env, argv) => {
const dev = argv.mode === "development";
return merge(webpackCommon, webpackReact, dev
? webpackDev({})
: webpackProd({}), {
plugins: [
new webpack.EnvironmentPlugin({
MODE: dev
? "development"
: "production"
})
],
resolve: {
alias: {
"~": path.resolve(__dirname, "src/"),
Api: path.resolve(__dirname, "src/api/"),
Components: path.resolve(__dirname, "src/components/"),
Models: path.resolve(__dirname, "src/models/"),
Services: path.resolve(__dirname, "src/services/"),
Stores: path.resolve(__dirname, "src/stores/"),
Views: path.resolve(__dirname, "src/views/")
}
}
});
};
FAQs
This is a module with all parallax-common-config configurations for team-parallax.
The npm package parallax-common-config receives a total of 0 weekly downloads. As such, parallax-common-config popularity was classified as not popular.
We found that parallax-common-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
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.