smashcast-common
This repository contains Gulp-based common tasks to make applications easier.
You can overwrite any task if you redefine it in your project's gulpfile.js
.
Optionally you can create a tasks.config.js
file which is for override the default task settings.
Install
Add your project's git remote before installing smashcast-common. This is required to generate default readme for your project.
$ npm i -D smashcast-common
A number of files that help keeping a standard accross smashcast-common host projects, will automatically copied to the host project. Note if any file already exists, the post-install will issue corresponding warnings.
Configuration
package.json
main
The main field is a module ID that is the primary entry point to your program. That is, if your package is named foo, and a user installs it, and then does require("foo"), then your main module's exports object will be returned.
This should be a module ID relative to the root of your package folder.
Set the main property to lib/index.js
, if you changed the distFolder in your config file, use your folder name instead of lib.
Sample config file.
This file is optional!
These are the default values:
// tasks.config.js moduleexports = app: buildPattern: '!(*.spec).js' testPattern: '*.spec.js' stylesheets: buildPattern: '*.scss' srcFolder: 'src' distFolder: 'lib' testsFolder: 'tests' // For integration and e2e tests targetBuild: 'browser' // browser / node;
targetBuild
Test task will be configured based on this property.
browser: Karma will run the tests in a browser (PhantomJS by default). node: Server side testing with Mocha.
Default value is browser.
Sample gulpfile
// gulpfile.js const gulp = ;const smashcastCommon = ; smashcastCommon; // Optional override or additional task// gulp.task('freeze', _ => console.log('Do some freezing')) // With nothing overriden, all smashcast host projects support:// lint, lint:JS, lint:CSS, nsp, ncu, test, server, build and clean
Contributing to this project
Git Commit Message Conventions
With this repository, we follow the angular's contributing guide. Every time you do a commit, a script will validate your message, and can prevent wrongly formatted commits.
More info, examples: https://docs.google.com/document/d/1QrDFcIiPjSLDn3EL15IJygNPiHORgU1_OOAqWjiDU5Y
Changing any of template/default files
All changes to smashcast-common template files must be marked as "BREAKING CHANGE" in the git commit footer describing what has changed and how client projects may update their existing files.
New template/default files
While also new files should be marked as breaking changes, if the client does not have that file yet, the post-install will still copy it automatically and the client project will not need to make any manual changes.
Gulp tasks
Test
Run all the tests found in the codebase using Karma for frontend testing or mocha for node testing. Define your environment in config file (targetBuild).
Usage
Run unit tests once
gulp test
Run unit tests continuously, on any src file change
gulp test:unit:watch
Run integration/e2e tests once
gulp test:integration
Run unit tests continuously, on any src file change
gulp test:integration:watch
Create test coverage into reports folder
gulp test:coverage
Run coverage, unit and integration/e2e tests once
gulp test
Lint
You can run separately or both javascript and style lint tasks.
To make lint tasks pass even if you have an error, use --relax
parameter. (gulp lint --relax
)
both
gulp lint
js
gulp lint:JS
style
gulp lint:CSS
NCU
Check if your dependencies have a new version.
gulp ncu
NSP
Check if any of your dependencies have a known vulnerability.
gulp ncu
Build
It is used to build JavaScript files. It uses Babel to compile ES6 code to ES5. It creates separate files in the build target directory.
The target directory is cleared before every build.
Usage
gulp build
Run it continuously, on any src file change
gulp build:watch
Release
Release your library.
Commit your changes before running this task.
- Run lint and test tasks
- Create build
- Update package version - version number detected by commit messages
- Generate changelog from commit messages
- Update version number in readme file
- Commit and push everything with the new version tag
- Post a message to #dev channel on slack with the version number and a link to the changelog
Usage
gulp release
Test-Servers
By default http and https servers will be created for frontend projects. Port numbers and other options can be changed through the config. Please see config.js for the default options.
Usage
gulp server