
Research
/Security News
Intercom’s npm Package Compromised in Ongoing Mini Shai-Hulud Worm Attack
Compromised intercom-client@7.0.4 npm package is tied to the ongoing Mini Shai-Hulud worm attack targeting developer and CI/CD secrets.
@holisticon/angular-common
Advanced tools
DEPRECATED , use Angular-CLI instead
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 appConfig = {
srcPath: 'src/main/frontend',
testPath: 'src/test/frontend',
junit: {
name: 'My-TestApp',
dir: 'target/surefire-reports'
},
};
module.exports = appConfig;
And provide 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"
},
...
Configure proxy:
proxy: {
'*': {
headers: {"Access-Control-Allow-Origin": "http://localhost:3000", "Access-Control-Allow-Credentials": "true"},
target: 'http://localhost:8080',
secure: false
}
}
Add your module here:
...
var appConfig = {
entryModule: path.resolve(sourceRoot, 'app/app.module#AppModule')
...
If you need to debug the tests use the node-inspector:
npm run debug
node-inspector --web-port=8282
You can then open chrome at http://127.0.0.1:8282/?port=5858 for debugging.
If you want to have verbose logging add NODE_DEBUG=holisticon_angular-common:
NODE_DEBUG=holisticon_angular-common npm run build
var path = require("path"),
srcPath = 'src/main/frontend',
testPath = 'src/test/frontend',
sourceRoot = path.resolve(__dirname, '..', srcPath);
var appConfig = {
srcPath: srcPath,
testPath: testPath,
copy: [{
from: sourceRoot + '/img',
to: 'img'
}, {
from: sourceRoot + '/i18n',
to: 'i18n'
}],
entry: {
'polyfills': sourceRoot + '/polyfills.browser.ts',
'app': sourceRoot + '/main.browser.ts',
'app2': sourceRoot + '/customer.browser.ts'
},
...
};
module.exports = appConfig;
...
var appConfig = {
...
watchURL: 'http://localhost:3000/?ionicplatform=ios',
...
};
module.exports = appConfig;
...
var appConfig = {
...
junit: {
title: 'MyProject',
dir: 'dist/test-reports'
},
...
};
module.exports = appConfig;
If you want to build a PWA, you can utilize the included Offline-Plugin. Just enter an option pwa with the configuration options:
...
var appConfig = {
...
pwa: {
// see https://github.com/NekR/offline-plugin/blob/master/docs/options.md
},
...
};
module.exports = appConfig;
Add entries to the property additionalWebpackOptions:
...
additionalWebpackOptions: {
plugins: [
/* use only de and en locale */
new webpack.NormalModuleReplacementPlugin(
/moment[\/\\]locale$/,
/de|en/
),
new webpack.optimize.CommonsChunkPlugin({
name: ['polyfills', 'vendor','common']
}),
]
},
module.exports = appConfig;
FAQs
Common angular build module for Angular 2
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.

Research
/Security News
Compromised intercom-client@7.0.4 npm package is tied to the ongoing Mini Shai-Hulud worm attack targeting developer and CI/CD secrets.

Research
Socket detected a malicious supply chain attack on PyPI package lightning versions 2.6.2 and 2.6.3, which execute credential-stealing malware on import.

Research
A brand-squatted TanStack npm package used postinstall scripts to steal .env files and exfiltrate developer secrets to an attacker-controlled endpoint.