
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.
@holisticon/angular-common
Advanced tools
A simple module for Angular 2, that encapsulates the complete Webpack build and just requires some basic configuration in the using Angular2 projects without hassle around with the build
npm install @holisticon/angular-common --save-dev
Or if you want to use the development version (nightly build), which maybe not stable!:
npm install @holisticon/angular-common@next --save-dev
var path = require("path");
// resolve paths
var sourceRoot = path.resolve(__dirname, '..', 'src', 'main', 'frontend'),
testRoot = path.resolve(__dirname, '..', 'src', 'test', 'frontend'),
distRoot = path.resolve(__dirname, '..', 'src', 'main', 'resources', 'static');
// overwrite defaults
var appConfig = {
srcPath: 'src/main/frontend',
testPath: 'src/test/frontend',
entry: {
app: sourceRoot + '/scripts/app.js',
salesboard: sourceRoot + '/scripts/app.salesboard.js',
assignment: sourceRoot + '/scripts/app.assignment.js'
},
srcApp: path.resolve(sourceRoot, 'app'),
testApp: path.resolve(testRoot, 'specs'),
srcSASS: path.resolve(sourceRoot, 'scss'),
srcI18N: path.resolve(sourceRoot, 'app', 'i18n'),
srcIMG: path.resolve(sourceRoot, 'img'),
dist: distRoot
};
module.exports = appConfig;
And provide a dummy files for
process.env['APP_CONFIG'] = require("path").resolve(__dirname, 'etc', 'appConfig.js');
module.exports = require('@holisticon/angular-common').karma;
process.env['APP_CONFIG'] = require("path").resolve(__dirname, 'etc', 'appConfig.js');
module.exports = require('@holisticon/angular-common').karma_ci;
process.env['APP_CONFIG'] = require("path").resolve(__dirname, 'etc', 'appConfig.js');
module.exports = require('@holisticon/angular-common').webpack;
...
"scripts": {
"start": "npm install && npm run watch",
"watch": "cross-env NODE_ENV=development webpack-dev-server --hot --inline --colors --progress --display-error-details --port 3000 ",
"build": "cross-env NODE_ENV=production webpack",
"test": "cross-env NODE_ENV=test karma start etc/karma.conf.ci.js",
"debug": "cross-env NODE_ENV=test karma start etc/karma.conf.js"
},
...
TODO multi-app
FAQs
Common angular build module for Angular 2
The npm package @holisticon/angular-common receives a total of 8 weekly downloads. As such, @holisticon/angular-common popularity was classified as not popular.
We found that @holisticon/angular-common demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 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
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.