reduct/build-tools

DEPRECATED

build-tools's Issues

Add a release task

The specs of the task:

• Fetch the commits since the last release, and write them down in markdown syntax in the CHANGELOG.md
• Paste all contributors into the package.json
• Ups the version number in the package.json (based on the second argument of the task f.e. reduct release minor
• Creates a git tag with the according message and version number

Implement the isTestingEnv boolean check

As discussed in our last meeting, we should integrate the isTestingEnv boolean into the UMD-Wrapper module.

Both the version and the isTestingEnv should be exported through the UMD-Wrapper factory in a options object.

Document all methods via the discussed JSDoc subset

Create the .lcov coverage result file for code-climate in the test task.

Create a script which automatically builds all source files

We should integrate a central build script which:

• Transpiles the files with Babel
• Adds a banner comment on top of each file. As seen on line 1
• Creates the semver oriented version object and adds it to the exports.
• Automatically wraps the whole source file into the export IIFE which handles all module systems. As seen on line 3-20
• Adds a minified version of the transpiled build into the Dist directory.

Use browserify as a dependency bundler

We need to find a way for bundling dependencies while running the build task.

Prior to the last week this wasn't needed since every package should be independent from each other. But with the separation of the logger and the oncoming framework abstraction-layer, we need a way to bundle up dependencies.

ENOENT Error while running JSCS

While running JSCS, I always get the error

{ [Error: ENOENT: no such file or directory, open './reports/jscs.json']

This error doesn't exit the task itself, so the validation still works properly.

Write the coding guidelines

The guidelines should explain the use of the used JSCS/ESLint rules, as well as some best practices.

Create tests for the build-tools

Set the babel stage to '0' per default

The babel/register hook doesn't seem to work when installed via npm

While developing the build tools I was using the npm link feature. Since migrating the assembler package to the regular npm install script, I get errors with all files containing ES6 code while running the reduct binary.

@akoenig @grebaldi

Accessing/Running the scripts from other packages

We should decide how we access the scripts of shared-build in our packages.
My first guess would be to write a node binary cli script which handles all arguments and then decides which sub-script will be executed(lint, build, test etc.). For example:

node Index.js build Assembler Src/ Dist/

which would take:

• 1: Assembler as the filename
• 2: Src as source folder
• 3: Dist as distribution folder

which then transpiles/compiles the Src/Assembler.js.

@akoenig you definitely know more about stuff like this, is this proposal utter bullshit? 🔍

Create git-hooks

Which check the commit messages against the guidelines, as well as the lint status.

Initiate the global window.reduct object in the UMD-Wrapper

Integrate the standard unit-test suite

Consisting of Mocha, Chai and JSDom...