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.
@eccenca/gulp-tasks
Advanced tools
Changelog
[3.17.0] 2019-06-03
eslint-plugin-jest
to allow eslint for jestReadme
A set of common gulp tasks for front-end development
Simply run gulp doctor --env
to check whether your environment matches the recommended environment and get installation instructions if not.
bad-mdl
- finds several bad mdl classes. We want to use the ecc-gui-elements instead of using those bad classes directly.build
- compiles optimized (minified, deduped) commonjs version of your component with webpack. Uses config.webpackConfig.production
as basic configuration.build-app
- compiles optimized (minified, deduped) application with webpack. Uses config.webpackConfig.application
as basic configuration.debug
- compiles debug version of your component with webpack, watches for changes and re-compiles when needed (until interrupted). Uses config.webpackConfig.debug
as basic configuration.test
- runs mocha tests starting from file specified at config.testEntryPoint
.cover
- runs istanbul to generate test coverage from file specified at config.testEntryPoint
.lint
- runs eslint on files specified at config.lintingFiles
.licenses-yaml2json
- generates a licenses.json
from a licenses.yaml
file.doctor
- runs several checks in the project. Some of them are fixable by running gulp doctor --heal
docs
creates a README.md from react code and template filenpm i --save-dev @eccenca/gulp-tasks
gulpfile.js
looks like this:var gulp = require('@eccenca/gulp-tasks')(require('./buildConfig.js'));
gulp.task('default', ['debug', 'serve']);
As you can see, you need to provide two arguments while requiring the package. First one is an array of string names of available tasks you wish to use. The second one is your build config (described below).
If you need to use your custom gulp tasks after including common ones, you can do it like so:
var gulp = require('@eccenca/gulp-tasks')(/* ... */);
// define task inline
gulp.task('my-task', function() {
// ...
});
// load your custom tasks from external file
require('./gulp/my-other-task.js')(gulp);
// ...
Normally gulp runs everything asynchronously, but sometimes you might want to run tasks in sync. That is useful for example if you want to run tests and then build a component. To do that, you can use gulp-sequence package, like so:
var gulpSequence = require('gulp-sequence');
var gulp = require('@eccenca/gulp-tasks')(/* ... */);
// ....
gulp.task('deploy', gulpSequence('test', 'build-app'));
Example build config looks like this:
var path = require('path');
module.exports = {
testEntryPoint: path.join(__dirname, 'test', 'index.jsx'),
webpackConfig: {
debug: require('./webpack.config.js'),
production: require('./webpack.config.prod.js'),
application: require('./webpack.config.app.js'),
common: {
context: path.resolve(__dirname),
},
},
licenseReport: {
input: path.resolve(__dirname, 'license-report.yaml'),
outputName: 'licenses.json',
outputPath: path.resolve(__dirname, 'dist')
},
};
Exported parameters are as follows:
testEntryPoint
- should point to your test entry point (to be run by mocha)webpackConfig.debug
- should include your webpack config used for debuggingwebpackConfig.production
- should include your webpack config used for compilation for productionwebpackConfig.application
- should include your webpack config used for compilation as production application. It allows for the following special parameters:
browsers
: a browserslist definition which is used for css autoprefixingcopyFiles
: a list of copy-webpack-plugin patterns which is used for copying files to the output folderhtml
: a html template for the html-webpack-pluginwebpackConfig.common
- may webpack config that webpackConfig.debug
, webpackConfig.production
and webpackConfig.application
have in commonlicenseReport
- should point to a license yaml file and contain parameters for the generated license reportThere are the following flags set:
__WEBPACK__
is set to true while using gulp build|build-app|debug
.
This may be used for doing things only webpack can do, like requiring style sheets, etc:
if(__WEBPACK__){
require('./style.css')
}
__DEBUG__
is set to true
during gulp debug
.
If you run gulp build-app
, __DEBUG__
is set to false
, effectively stripping all debug statements.
This may be used for doing things only during development:
// The following block will only be run during development
if(__DEBUG__){
console.info('Dear Developer, have a nice day')
}
__VERSION__
is set to 'VERSION'
If the environment variable GT_BUILD_VERSION
is set, __VERSION__
will be set to that value.
Otherwise it will be set to the result of git describe --always --dirty
, if that does not fail.
Usage:
const version = (<div>{__VERSION__}</div>);
To use docs
following rules must be minded:
For examples look at test/fixtures/docs/Store.jsx
FAQs
A set of common gulp tasks for front-end development.
The npm package @eccenca/gulp-tasks receives a total of 11 weekly downloads. As such, @eccenca/gulp-tasks popularity was classified as not popular.
We found that @eccenca/gulp-tasks demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 5 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.