just-task uses the best pirate themed command line argument library ever: yargs, matey! So, rigs get documented pretty much automatically. However, tasks can customize the arguments that are accepted. just-task exposes these via this.argv inside a task function.
-
Reading arguments
-
To read the arguments passed in from command line, use the argv() function provided by yargs.
\ No newline at end of file
diff --git a/docs/docs/args/index.html b/docs/docs/args/index.html
deleted file mode 100644
index d923508d..00000000
--- a/docs/docs/args/index.html
+++ /dev/null
@@ -1,83 +0,0 @@
-Command line arguments · Just ____
just-task uses the best pirate themed command line argument library ever: yargs, matey! So, rigs get documented pretty much automatically. However, tasks can customize the arguments that are accepted. just-task exposes these via this.argv inside a task function.
-
Reading arguments
-
To read the arguments passed in from command line, use the argv() function provided by yargs.
\ No newline at end of file
diff --git a/docs/docs/composition.html b/docs/docs/composition.html
deleted file mode 100644
index 1b6b5fc3..00000000
--- a/docs/docs/composition.html
+++ /dev/null
@@ -1,104 +0,0 @@
-Composition of tasks · Just ____
Once a project gets a bit more complex, a build step might consist of multiple sub tasks. This can be achieved with composition. This is the main reason just-task was made. It simplifies the composition of tasks.
-
Running tasks in a series
-
const { task, series } = require('just-task');
-
-task('clean', function() {
- // clean stuff
-});
-
-task('babel', function() {
- // run babel over some files
-});
-
-task('build', series('clean', 'babel'));
-
-
When you trigger just build, the clean task will run and complete before babel task is run.
-
Running tasks in parallel
-
To take advantage of multi-core CPUs on our machines, we can run several tasks in parallel. Simply use the parallel() function.
-
const { task, parallel } = require('just-task');
-
-task('babel', function() {
- // run babel babel over some files
-});
-
-task('lint', function() {
- // run eslint over some files
-});
-
-task('build', parallel('babel', 'lint'));
-
-
Nesting tasks in series and parallel
-
The most powerful feature of just-task is its ability to compose tasks by nesting tasks in series and parallel. Let's combine the previous examples.
-
const { task, parallel, series } = require('just-task');
-
-task('babel', function() {
- // run babel babel over some files
-});
-
-task('lint', function() {
- // run eslint over some files
-});
-
-task('build', series('clean', parallel('babel', 'lint')));
-
\ No newline at end of file
diff --git a/docs/docs/composition/index.html b/docs/docs/composition/index.html
deleted file mode 100644
index 1b6b5fc3..00000000
--- a/docs/docs/composition/index.html
+++ /dev/null
@@ -1,104 +0,0 @@
-Composition of tasks · Just ____
Once a project gets a bit more complex, a build step might consist of multiple sub tasks. This can be achieved with composition. This is the main reason just-task was made. It simplifies the composition of tasks.
-
Running tasks in a series
-
const { task, series } = require('just-task');
-
-task('clean', function() {
- // clean stuff
-});
-
-task('babel', function() {
- // run babel over some files
-});
-
-task('build', series('clean', 'babel'));
-
-
When you trigger just build, the clean task will run and complete before babel task is run.
-
Running tasks in parallel
-
To take advantage of multi-core CPUs on our machines, we can run several tasks in parallel. Simply use the parallel() function.
-
const { task, parallel } = require('just-task');
-
-task('babel', function() {
- // run babel babel over some files
-});
-
-task('lint', function() {
- // run eslint over some files
-});
-
-task('build', parallel('babel', 'lint'));
-
-
Nesting tasks in series and parallel
-
The most powerful feature of just-task is its ability to compose tasks by nesting tasks in series and parallel. Let's combine the previous examples.
-
const { task, parallel, series } = require('just-task');
-
-task('babel', function() {
- // run babel babel over some files
-});
-
-task('lint', function() {
- // run eslint over some files
-});
-
-task('build', series('clean', parallel('babel', 'lint')));
-
\ No newline at end of file
diff --git a/docs/docs/condition.html b/docs/docs/condition.html
deleted file mode 100644
index 91b9aaa1..00000000
--- a/docs/docs/condition.html
+++ /dev/null
@@ -1,103 +0,0 @@
-Controlling Task Flow with Conditionals · Just ____
Sometimes a just-task.js includes tasks that are skipped depending on the arguments that are given. Use a condition() function to decide to run a task or to skip it.
-
Running tasks in a series
-
As we have seen, tasks can be run in a series.
-
const { task, series } = require('just-task');
-
-task('clean', function() {
- // clean stuff
-});
-
-task('babel', function() {
- // run babel over some files
-});
-
-task('test', function() {
- // run babel over some files
-});
-
-task('build', series('clean', 'babel', 'test'));
-
-
We can conditionally skip the test task by some argument like --skip-test
-
const { task, series, option, argv, condition } = require('just-task');
-
-// First define a 'skip-test' option
-option('skip-test');
-
-task('clean', function() {
- // clean stuff
-});
-
-task('babel', function() {
- // run babel over some files
-});
-
-task('test', function() {
- // run babel over some files
-});
-
-task('build', series('clean', 'babel', condition('test', () => !argv()['skip-test'])));
-
-
Now you can skip the test task by passing an argument like this:
\ No newline at end of file
diff --git a/docs/docs/condition/index.html b/docs/docs/condition/index.html
deleted file mode 100644
index 91b9aaa1..00000000
--- a/docs/docs/condition/index.html
+++ /dev/null
@@ -1,103 +0,0 @@
-Controlling Task Flow with Conditionals · Just ____
Sometimes a just-task.js includes tasks that are skipped depending on the arguments that are given. Use a condition() function to decide to run a task or to skip it.
-
Running tasks in a series
-
As we have seen, tasks can be run in a series.
-
const { task, series } = require('just-task');
-
-task('clean', function() {
- // clean stuff
-});
-
-task('babel', function() {
- // run babel over some files
-});
-
-task('test', function() {
- // run babel over some files
-});
-
-task('build', series('clean', 'babel', 'test'));
-
-
We can conditionally skip the test task by some argument like --skip-test
-
const { task, series, option, argv, condition } = require('just-task');
-
-// First define a 'skip-test' option
-option('skip-test');
-
-task('clean', function() {
- // clean stuff
-});
-
-task('babel', function() {
- // run babel over some files
-});
-
-task('test', function() {
- // run babel over some files
-});
-
-task('build', series('clean', 'babel', condition('test', () => !argv()['skip-test'])));
-
-
Now you can skip the test task by passing an argument like this:
\ No newline at end of file
diff --git a/docs/docs/doc-start.html b/docs/docs/doc-start.html
deleted file mode 100644
index 8d2c9f65..00000000
--- a/docs/docs/doc-start.html
+++ /dev/null
@@ -1,78 +0,0 @@
-Getting Started with Just · Just ____
Just simplifies your life in managing build tasks. It stands on the shoulders of excellent and well tested libraries: undertaker, yargs, and plop.js. We encourage developers to make just-scripts available locally instead of installing just-scripts as a global tool.
-
npm i -D just-scripts
-
-
Place some task definitions inside just.config.js in your root folder (next to package.json):
\ No newline at end of file
diff --git a/docs/docs/doc-start/index.html b/docs/docs/doc-start/index.html
deleted file mode 100644
index 8d2c9f65..00000000
--- a/docs/docs/doc-start/index.html
+++ /dev/null
@@ -1,78 +0,0 @@
-Getting Started with Just · Just ____
Just simplifies your life in managing build tasks. It stands on the shoulders of excellent and well tested libraries: undertaker, yargs, and plop.js. We encourage developers to make just-scripts available locally instead of installing just-scripts as a global tool.
-
npm i -D just-scripts
-
-
Place some task definitions inside just.config.js in your root folder (next to package.json):
\ No newline at end of file
diff --git a/docs/docs/logging.html b/docs/docs/logging.html
deleted file mode 100644
index 09eced13..00000000
--- a/docs/docs/logging.html
+++ /dev/null
@@ -1,88 +0,0 @@
-Logging · Just ____
just-task is simple, but it is opinionated. One of the built-in capabilities of just-task is logging. We feel that this is an important enough of a feature to be available by the library.
-
Typically, logging tasks look like the following:
-
-
Usage
-
To log within the task, simply use the info() function off of the logger object inside a task function.
\ No newline at end of file
diff --git a/docs/docs/logging/index.html b/docs/docs/logging/index.html
deleted file mode 100644
index 09eced13..00000000
--- a/docs/docs/logging/index.html
+++ /dev/null
@@ -1,88 +0,0 @@
-Logging · Just ____
just-task is simple, but it is opinionated. One of the built-in capabilities of just-task is logging. We feel that this is an important enough of a feature to be available by the library.
-
Typically, logging tasks look like the following:
-
-
Usage
-
To log within the task, simply use the info() function off of the logger object inside a task function.
\ No newline at end of file
diff --git a/docs/docs/scripts-jest.html b/docs/docs/scripts-jest.html
deleted file mode 100644
index 745a5749..00000000
--- a/docs/docs/scripts-jest.html
+++ /dev/null
@@ -1,85 +0,0 @@
-Jest · Just ____
Jest is one of the most popular testing libraries in the Javascript ecosystem. It is also a preset supported out of the box inside the just-scripts library. Similar to the other presets, this task function assumes that you have a jest.config.js at the root of the project.
\ No newline at end of file
diff --git a/docs/docs/scripts-jest/index.html b/docs/docs/scripts-jest/index.html
deleted file mode 100644
index 745a5749..00000000
--- a/docs/docs/scripts-jest/index.html
+++ /dev/null
@@ -1,85 +0,0 @@
-Jest · Just ____
Jest is one of the most popular testing libraries in the Javascript ecosystem. It is also a preset supported out of the box inside the just-scripts library. Similar to the other presets, this task function assumes that you have a jest.config.js at the root of the project.
\ No newline at end of file
diff --git a/docs/docs/scripts-ts.html b/docs/docs/scripts-ts.html
deleted file mode 100644
index 15178951..00000000
--- a/docs/docs/scripts-ts.html
+++ /dev/null
@@ -1,76 +0,0 @@
-TypeScript · Just ____
TypeScript is a very popular compiler that allows developers to use modern ES6 features as well as a very mature typing system. The benefits are so great that it has become one of the first presets supported by the just-scripts library.
-
Given a library with TypeScript source code, it might be desirable to have multiple output formats for different audiences. By default, the tscTask() function looks for the tsconfig.json present in the project root. The preset higher order function can take in an option that overrides compilation options. The TypeScript compiler options are passed to the tsc.js script.
-
A list of available options are located at the TypeScript documentation site. The options passed into the preset function will be passed in as command line arguments as a string.
\ No newline at end of file
diff --git a/docs/docs/scripts-ts/index.html b/docs/docs/scripts-ts/index.html
deleted file mode 100644
index 15178951..00000000
--- a/docs/docs/scripts-ts/index.html
+++ /dev/null
@@ -1,76 +0,0 @@
-TypeScript · Just ____
TypeScript is a very popular compiler that allows developers to use modern ES6 features as well as a very mature typing system. The benefits are so great that it has become one of the first presets supported by the just-scripts library.
-
Given a library with TypeScript source code, it might be desirable to have multiple output formats for different audiences. By default, the tscTask() function looks for the tsconfig.json present in the project root. The preset higher order function can take in an option that overrides compilation options. The TypeScript compiler options are passed to the tsc.js script.
-
A list of available options are located at the TypeScript documentation site. The options passed into the preset function will be passed in as command line arguments as a string.
\ No newline at end of file
diff --git a/docs/docs/scripts-tslint.html b/docs/docs/scripts-tslint.html
deleted file mode 100644
index 09198525..00000000
--- a/docs/docs/scripts-tslint.html
+++ /dev/null
@@ -1,64 +0,0 @@
-TypeScript Lint · Just ____
TypeScript is a very popular compiler. But as the amount of code grows, developers need a way to keep the code looking consistent. tslint is the de facto linter for TS code.
\ No newline at end of file
diff --git a/docs/docs/scripts-tslint/index.html b/docs/docs/scripts-tslint/index.html
deleted file mode 100644
index 09198525..00000000
--- a/docs/docs/scripts-tslint/index.html
+++ /dev/null
@@ -1,64 +0,0 @@
-TypeScript Lint · Just ____
TypeScript is a very popular compiler. But as the amount of code grows, developers need a way to keep the code looking consistent. tslint is the de facto linter for TS code.
\ No newline at end of file
diff --git a/docs/docs/scripts-webpack.html b/docs/docs/scripts-webpack.html
deleted file mode 100644
index 54a3eced..00000000
--- a/docs/docs/scripts-webpack.html
+++ /dev/null
@@ -1,86 +0,0 @@
-Webpack · Just ____
Webpack is the Javascript, CSS and asset bundler that powers some of the largest Web applications. Just Scripts comes with great integration with Webpack out of the box. All of the power of Webpack comes at the cost of complexity in its configuration. The bundler actually comes with great defaults. However, it takes some non-trivial amount of config to make it work with transpilers like TypeScript.
-
just-scripts exports a flexible Webpack just-task task function. Unlike create-react-app, just-scripts does not require ejecting to allow customizations of the Webpack configuration. just-scripts abstracts the complexity of the configuration with what is known as "Overlays". For example, to add support of TypeScript transpilation, several parts of the configuration needs to be changed to support the various parts of building with TypeScript.
-
This task function will look for two files at the root of the project:
-
-
webpack.config.js
-
webpack.serve.config.js
-
-
The Webpack task function will use webpack.config.js for its optimized production builds. It will use the webpack.serve.config.js for innerloop development.
-
Example webpack.config.js and webpack.serve.config.js
-
The webpack.config.js and webpack.serve.config.js can be completely customized to your own needs. However, some great utilities from just-scripts make it really easy to get going. Take a look at an example webpack.config.js that uses these utilities:
From this example, several concepts are illustrated. First, you can see that just-scripts exposes:
-
-
webpackMerge: this is just a thin wrapper on top of the excellent webpack-merge package
-
webpackServeConfig: this a very basic preset configuration that you can use as a baseline, there is also a webpackConfig module exported that you can use for your webpack.config.js
-
htmlOverlay: this is one of the overlays that adds some functionality to Webpack to be merged by the webpack-merge utility
-
-
Overlays
-
These overlays are not configurable (for now), but they do provide a great baseline to start from.
-
-
fileOverlay: This adds the file-loader to allow loading SVG, PNG, GIF, JPG files
-
htmlOverlay: This adds the html-webpack-plugin that generates the right code to include scripts and other assets into your index.html
-
stylesOverlay: This adds styling support for both CSS and Sass
-
tsOverlay: This adds a ts-loader transpilation support for TypeScript files while configuring a fork-ts-checker-webpack-plugin for typechecking in a separate process for the fastest compilation experience
\ No newline at end of file
diff --git a/docs/docs/scripts-webpack/index.html b/docs/docs/scripts-webpack/index.html
deleted file mode 100644
index 54a3eced..00000000
--- a/docs/docs/scripts-webpack/index.html
+++ /dev/null
@@ -1,86 +0,0 @@
-Webpack · Just ____
Webpack is the Javascript, CSS and asset bundler that powers some of the largest Web applications. Just Scripts comes with great integration with Webpack out of the box. All of the power of Webpack comes at the cost of complexity in its configuration. The bundler actually comes with great defaults. However, it takes some non-trivial amount of config to make it work with transpilers like TypeScript.
-
just-scripts exports a flexible Webpack just-task task function. Unlike create-react-app, just-scripts does not require ejecting to allow customizations of the Webpack configuration. just-scripts abstracts the complexity of the configuration with what is known as "Overlays". For example, to add support of TypeScript transpilation, several parts of the configuration needs to be changed to support the various parts of building with TypeScript.
-
This task function will look for two files at the root of the project:
-
-
webpack.config.js
-
webpack.serve.config.js
-
-
The Webpack task function will use webpack.config.js for its optimized production builds. It will use the webpack.serve.config.js for innerloop development.
-
Example webpack.config.js and webpack.serve.config.js
-
The webpack.config.js and webpack.serve.config.js can be completely customized to your own needs. However, some great utilities from just-scripts make it really easy to get going. Take a look at an example webpack.config.js that uses these utilities:
From this example, several concepts are illustrated. First, you can see that just-scripts exposes:
-
-
webpackMerge: this is just a thin wrapper on top of the excellent webpack-merge package
-
webpackServeConfig: this a very basic preset configuration that you can use as a baseline, there is also a webpackConfig module exported that you can use for your webpack.config.js
-
htmlOverlay: this is one of the overlays that adds some functionality to Webpack to be merged by the webpack-merge utility
-
-
Overlays
-
These overlays are not configurable (for now), but they do provide a great baseline to start from.
-
-
fileOverlay: This adds the file-loader to allow loading SVG, PNG, GIF, JPG files
-
htmlOverlay: This adds the html-webpack-plugin that generates the right code to include scripts and other assets into your index.html
-
stylesOverlay: This adds styling support for both CSS and Sass
-
tsOverlay: This adds a ts-loader transpilation support for TypeScript files while configuring a fork-ts-checker-webpack-plugin for typechecking in a separate process for the fastest compilation experience
\ No newline at end of file
diff --git a/docs/docs/scripts.html b/docs/docs/scripts.html
deleted file mode 100644
index e6e0311c..00000000
--- a/docs/docs/scripts.html
+++ /dev/null
@@ -1,77 +0,0 @@
-Just Scripts · Just ____
Unlike other build libraries, Just strives to be useful from the beginning. You can choose to write your own tasks that call other Node.js tools like TypeScript, jest, and webpack. However, Just includes some script functions to get you up and running immediately. The included tasks are enough to have a very productive environment without dictating a certain stack to be used with Just.
-
-
NOTE: even though just-scripts interacts with typescript, it does not take typescript as a dependency. It assumes that the developers will include that in their own projects. This gives just-scripts the flexibility of targeting many different versions of individual build tools without imposing a version on the consumers.
-
-
These scripts are coded as higher order task functions. Each of these script functions return a task function to be registered as a task in your own just-task.js like this:
Generally, these higher order functions also take an options argument to generate a specific task function preconfigured according to the options. For example:
\ No newline at end of file
diff --git a/docs/docs/scripts/index.html b/docs/docs/scripts/index.html
deleted file mode 100644
index e6e0311c..00000000
--- a/docs/docs/scripts/index.html
+++ /dev/null
@@ -1,77 +0,0 @@
-Just Scripts · Just ____
Unlike other build libraries, Just strives to be useful from the beginning. You can choose to write your own tasks that call other Node.js tools like TypeScript, jest, and webpack. However, Just includes some script functions to get you up and running immediately. The included tasks are enough to have a very productive environment without dictating a certain stack to be used with Just.
-
-
NOTE: even though just-scripts interacts with typescript, it does not take typescript as a dependency. It assumes that the developers will include that in their own projects. This gives just-scripts the flexibility of targeting many different versions of individual build tools without imposing a version on the consumers.
-
-
These scripts are coded as higher order task functions. Each of these script functions return a task function to be registered as a task in your own just-task.js like this:
Generally, these higher order functions also take an options argument to generate a specific task function preconfigured according to the options. For example:
\ No newline at end of file
diff --git a/docs/docs/stacks-monorepo.html b/docs/docs/stacks-monorepo.html
deleted file mode 100644
index 71bcb17b..00000000
--- a/docs/docs/stacks-monorepo.html
+++ /dev/null
@@ -1,89 +0,0 @@
-Monorepo Stack · Just ____
When there are many highly related packages that are usually developed together, it makes sense to put them in the same repository. This ensures that those changes are atomic and can be released together in one go. When we put multiple packages inside a single repository, we call this a monorepo.
-
Just uses the Lerna library to manage monorepos together with yarn workspaces. Those libraries handles linking monorepo packages together to ensure a sane developer experience. Lerna is powerful, but it does not provide opinions about what kind of packages are scaffolded inside the monorepo. Just Stacks provides this for the monorepo.
-
Prerequisites
-
Yarn is a prerequisite in using the monorepo stack. Install it like so:
-
npm install -g yarn
-
-
Getting Started with the MonoRepo
-
After creating a monorepo, you can create packages, incrementally build all the packages, and even upgrade the packages according to changes from the templates by an upgrade process.
-
Installing dependencies
-
Installing dependencies is the job of Yarn. Install all dependencies and bootstrap the monorepo like so:
-
yarn
-
-
-
Like the single package stacks, don't forget to run yarn after you do a git pull
-
-
Building monorepo
-
To build all the packages, simply run the build npm script. Previously built packages will not be built. We call this incremental builds:
-
yarnbuild
-
-
To develop with an innerloop experience, go inside the individual package and type:
-
cd packages/foo
-yarn start
-
-
Adding a new package into the repo
-
Out of the box, the monorepo stack provides a mechanism to create new packages using the plop.js utility. Simply run this to generate a new package:
-
yarn gen
-
-
After picking a package name and a package type, the new package will be placed under packages/ directory. Make sure you update deps and symlink are established by Yarn:
\ No newline at end of file
diff --git a/docs/docs/stacks-monorepo/index.html b/docs/docs/stacks-monorepo/index.html
deleted file mode 100644
index 71bcb17b..00000000
--- a/docs/docs/stacks-monorepo/index.html
+++ /dev/null
@@ -1,89 +0,0 @@
-Monorepo Stack · Just ____
When there are many highly related packages that are usually developed together, it makes sense to put them in the same repository. This ensures that those changes are atomic and can be released together in one go. When we put multiple packages inside a single repository, we call this a monorepo.
-
Just uses the Lerna library to manage monorepos together with yarn workspaces. Those libraries handles linking monorepo packages together to ensure a sane developer experience. Lerna is powerful, but it does not provide opinions about what kind of packages are scaffolded inside the monorepo. Just Stacks provides this for the monorepo.
-
Prerequisites
-
Yarn is a prerequisite in using the monorepo stack. Install it like so:
-
npm install -g yarn
-
-
Getting Started with the MonoRepo
-
After creating a monorepo, you can create packages, incrementally build all the packages, and even upgrade the packages according to changes from the templates by an upgrade process.
-
Installing dependencies
-
Installing dependencies is the job of Yarn. Install all dependencies and bootstrap the monorepo like so:
-
yarn
-
-
-
Like the single package stacks, don't forget to run yarn after you do a git pull
-
-
Building monorepo
-
To build all the packages, simply run the build npm script. Previously built packages will not be built. We call this incremental builds:
-
yarnbuild
-
-
To develop with an innerloop experience, go inside the individual package and type:
-
cd packages/foo
-yarn start
-
-
Adding a new package into the repo
-
Out of the box, the monorepo stack provides a mechanism to create new packages using the plop.js utility. Simply run this to generate a new package:
-
yarn gen
-
-
After picking a package name and a package type, the new package will be placed under packages/ directory. Make sure you update deps and symlink are established by Yarn:
\ No newline at end of file
diff --git a/docs/docs/stacks-single.html b/docs/docs/stacks-single.html
deleted file mode 100644
index 325a282b..00000000
--- a/docs/docs/stacks-single.html
+++ /dev/null
@@ -1,83 +0,0 @@
-Single Stack · Just ____
The simplest kind of projects are the single package repositories. Out of the box, just can create a single package library or a batteries-included web application. The generated repository will use the just library to manage its build definitions. You can customize the build task flow by editing the just.config.js at the root of the generated repository.
-
To get started, have a look at the README.md at the root of the newly generated repository. Some of the common commands are listed here.
-
Installing dependencies
-
Installing dependencies is the job of the package manager. By default node.js comes with the npm package manager. We can simply do this:
-
npm install
-
-
-
Don't forget to run npm install after you do a git pull
-
-
Building package
-
To build the package, simply run the build npm script:
-
npm run build
-
-
To develop with an innerloop experience, type:
-
npm start
-
-
Testing the package
-
The jest library is used to run tests. This library can run unit tests in parallel and has a good developer experience when developing test by providing an innerloop capability via its watch mode.
\ No newline at end of file
diff --git a/docs/docs/stacks-single/index.html b/docs/docs/stacks-single/index.html
deleted file mode 100644
index 325a282b..00000000
--- a/docs/docs/stacks-single/index.html
+++ /dev/null
@@ -1,83 +0,0 @@
-Single Stack · Just ____
The simplest kind of projects are the single package repositories. Out of the box, just can create a single package library or a batteries-included web application. The generated repository will use the just library to manage its build definitions. You can customize the build task flow by editing the just.config.js at the root of the generated repository.
-
To get started, have a look at the README.md at the root of the newly generated repository. Some of the common commands are listed here.
-
Installing dependencies
-
Installing dependencies is the job of the package manager. By default node.js comes with the npm package manager. We can simply do this:
-
npm install
-
-
-
Don't forget to run npm install after you do a git pull
-
-
Building package
-
To build the package, simply run the build npm script:
-
npm run build
-
-
To develop with an innerloop experience, type:
-
npm start
-
-
Testing the package
-
The jest library is used to run tests. This library can run unit tests in parallel and has a good developer experience when developing test by providing an innerloop capability via its watch mode.
\ No newline at end of file
diff --git a/docs/docs/stacks-upgrades.html b/docs/docs/stacks-upgrades.html
deleted file mode 100644
index 05b70091..00000000
--- a/docs/docs/stacks-upgrades.html
+++ /dev/null
@@ -1,66 +0,0 @@
-Upgrading Repos · Just ____
just-stack upgrades are done via updating two dependencies:
-
-
just-scripts
-
just-stack-*
-
-
The just-scripts dependency updates the build scripts. When new functionality has been added or updated, you can update this dependency. For example, eslint task has been added recently and can be used when the scripts package is updated.
-
Separately, the just-stack-* dependency contain all the devDependencies needed for the just-scripts. These are versioned independently because scripts and deps can be released at different times. For example, even if we added new scripts inside just-scripts, generated repos may still want to keep the current devDependencies so not to have interruptions.
\ No newline at end of file
diff --git a/docs/docs/stacks-upgrades/index.html b/docs/docs/stacks-upgrades/index.html
deleted file mode 100644
index 05b70091..00000000
--- a/docs/docs/stacks-upgrades/index.html
+++ /dev/null
@@ -1,66 +0,0 @@
-Upgrading Repos · Just ____
just-stack upgrades are done via updating two dependencies:
-
-
just-scripts
-
just-stack-*
-
-
The just-scripts dependency updates the build scripts. When new functionality has been added or updated, you can update this dependency. For example, eslint task has been added recently and can be used when the scripts package is updated.
-
Separately, the just-stack-* dependency contain all the devDependencies needed for the just-scripts. These are versioned independently because scripts and deps can be released at different times. For example, even if we added new scripts inside just-scripts, generated repos may still want to keep the current devDependencies so not to have interruptions.
\ No newline at end of file
diff --git a/docs/docs/stacks.html b/docs/docs/stacks.html
deleted file mode 100644
index 351779ba..00000000
--- a/docs/docs/stacks.html
+++ /dev/null
@@ -1,70 +0,0 @@
-Just Stacks · Just ____
Just also provides what we call "stacks" to complete the workflow of building a repository. Just Stacks provides:
-
-
a project generator for single package or monorepo repository via create-just
-
generated repo depends on a stack like just-stack-react and just-stack-monorepo which provides all the devDependencies needed to build those stacks
-
these stacks also take just-scripts as a dependency which gives the repos the necessary build scripting for different parts of the stack (compiler, test runner, and bundler)
-
-
Generate a new project
-
It is very fast and easy to get started! We have taken care to make this experience as fast as possible. You can create a project in a couple of seconds:
-
npm init just
-
-
From here, you can choose a type of project to scaffold. We'll take a look the different kinds in the next sections.
\ No newline at end of file
diff --git a/docs/docs/stacks/index.html b/docs/docs/stacks/index.html
deleted file mode 100644
index 351779ba..00000000
--- a/docs/docs/stacks/index.html
+++ /dev/null
@@ -1,70 +0,0 @@
-Just Stacks · Just ____
Just also provides what we call "stacks" to complete the workflow of building a repository. Just Stacks provides:
-
-
a project generator for single package or monorepo repository via create-just
-
generated repo depends on a stack like just-stack-react and just-stack-monorepo which provides all the devDependencies needed to build those stacks
-
these stacks also take just-scripts as a dependency which gives the repos the necessary build scripting for different parts of the stack (compiler, test runner, and bundler)
-
-
Generate a new project
-
It is very fast and easy to get started! We have taken care to make this experience as fast as possible. You can create a project in a couple of seconds:
-
npm init just
-
-
From here, you can choose a type of project to scaffold. We'll take a look the different kinds in the next sections.
\ No newline at end of file
diff --git a/docs/docs/thunk.html b/docs/docs/thunk.html
deleted file mode 100644
index 17e9b85e..00000000
--- a/docs/docs/thunk.html
+++ /dev/null
@@ -1,80 +0,0 @@
-Higher Order Task Functions · Just ____
When a project truly gets big enough to have multiple variants of a build, a simple task function might be reused as variants. For example, the just-task-preset package includes a useful collection of task functions like tscTask. However, these tasks tend to be very generic. tscTask() is a task function factory. Calling it will generate a task function. But sometimes variations of the same preconfigured task function is needed. We will use a concept called thunk to create a task function that creates a task function on the fly!
-
Here is an example of a simple usage of a preset task function factory:
\ No newline at end of file
diff --git a/docs/docs/thunk/index.html b/docs/docs/thunk/index.html
deleted file mode 100644
index 17e9b85e..00000000
--- a/docs/docs/thunk/index.html
+++ /dev/null
@@ -1,80 +0,0 @@
-Higher Order Task Functions · Just ____
When a project truly gets big enough to have multiple variants of a build, a simple task function might be reused as variants. For example, the just-task-preset package includes a useful collection of task functions like tscTask. However, these tasks tend to be very generic. tscTask() is a task function factory. Calling it will generate a task function. But sometimes variations of the same preconfigured task function is needed. We will use a concept called thunk to create a task function that creates a task function on the fly!
-
Here is an example of a simple usage of a preset task function factory:
\ No newline at end of file
diff --git a/docs/en/help.html b/docs/en/help.html
deleted file mode 100644
index 92af4a44..00000000
--- a/docs/en/help.html
+++ /dev/null
@@ -1,7 +0,0 @@
-Just ____ · The task library that just works
\ No newline at end of file
diff --git a/docs/en/help/index.html b/docs/en/help/index.html
deleted file mode 100644
index 92af4a44..00000000
--- a/docs/en/help/index.html
+++ /dev/null
@@ -1,7 +0,0 @@
-Just ____ · The task library that just works
\ No newline at end of file
diff --git a/docs/en/index.html b/docs/en/index.html
deleted file mode 100644
index d78fa4a6..00000000
--- a/docs/en/index.html
+++ /dev/null
@@ -1 +0,0 @@
-Just ____ · The task library that just works
\ No newline at end of file
diff --git a/docs/en/users.html b/docs/en/users.html
deleted file mode 100644
index 9081a3d0..00000000
--- a/docs/en/users.html
+++ /dev/null
@@ -1 +0,0 @@
-Just ____ · The task library that just works
\ No newline at end of file
diff --git a/docs/en/users/index.html b/docs/en/users/index.html
deleted file mode 100644
index 9081a3d0..00000000
--- a/docs/en/users/index.html
+++ /dev/null
@@ -1 +0,0 @@
-Just ____ · The task library that just works
\ No newline at end of file
diff --git a/docs/help.html b/docs/help.html
deleted file mode 100644
index 4e8f4542..00000000
--- a/docs/help.html
+++ /dev/null
@@ -1,7 +0,0 @@
-Just ____ · The task library that just works
\ No newline at end of file
diff --git a/docs/help/index.html b/docs/help/index.html
deleted file mode 100644
index 4e8f4542..00000000
--- a/docs/help/index.html
+++ /dev/null
@@ -1,7 +0,0 @@
-Just ____ · The task library that just works