lage 2.5.3 → 2.5.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,8 +1,8 @@
1
1
  # lage
2
2
 
3
- The documentation for `lage` currently located in [the /docs-beta path](https://github.com/microsoft/lage/tree/master/docs-beta/docs)
3
+ Documentation: https://microsoft.github.io/lage/
4
4
 
5
- This is the lateset release of lage. Please see [RELEASE.md] for more details of new features!
5
+ **Lage v2 is here!** See the [release notes](https://github.com/microsoft/lage/blob/master/packages/lage/RELEASE.md) for details about new features and breaking changes.
6
6
 
7
7
  ## Overview
8
8
 
@@ -14,17 +14,31 @@ This usually means that there are wasted CPU cycles in between `build` and `test
14
14
 
15
15
  `lage` (Norwegian for "make", pronounced law-geh) solves this by providing a terse pipelining syntax. It has many features geared towards speeding up the task runner that we'll explore later.
16
16
 
17
- ## Quick Start
17
+ ## Quick start
18
18
 
19
- `lage` gives you this capability with very little configuration. First, let's install the `lage` utility. You can place this in your workspace's root `package.json` by running `yarn add`:
19
+ `lage` gives you this capability with very little configuration.
20
+
21
+ ### Automatic installation
22
+
23
+ You can automatically install lage and create a basic config file by running:
20
24
 
21
25
  ```
22
- yarn add -D lage
26
+ npx lage init
23
27
  ```
24
28
 
25
- Confirm with `yarn` that you are sure to add a package at the root level, you then place a root level script inside the `package.json` to run `lage`:
29
+ ### Manual installation
30
+
31
+ You can also install and configure `lage` manually.
26
32
 
33
+ First, install `lage` at your workspace's root. For example, if you're using `yarn`:
34
+
35
+ ```
36
+ yarn add -D -W lage
27
37
  ```
38
+
39
+ Next, add scripts inside the workspace root `package.json` to run `lage`. For example:
40
+
41
+ ```json
28
42
  {
29
43
  "scripts": {
30
44
  "build": "lage build",
@@ -33,7 +47,7 @@ Confirm with `yarn` that you are sure to add a package at the root level, you th
33
47
  }
34
48
  ```
35
49
 
36
- Add a configuration file in the root to get started. Create this file at the root `lage.config.js`:
50
+ To specify that `test` depends on `build`, create a file `lage.config.js` at the repo root and add the following:
37
51
 
38
52
  ```js
39
53
  module.exports = {
@@ -44,25 +58,22 @@ module.exports = {
44
58
  };
45
59
  ```
46
60
 
47
- Do not worry about the syntax for now. We will go over the configuration file in a coming section. You can now run this command:
61
+ (You can find more details about this syntax in the [pipelines tutorial](https://microsoft.github.io/lage/docs/Tutorial/pipeline).)
62
+
63
+ You can now run this command:
48
64
 
49
65
  ```
50
- $ lage test
66
+ lage test
51
67
  ```
52
68
 
53
69
  `lage` will detect that you need to run `build` steps before `test`s are run.
54
70
 
71
+ ## Next steps
55
72
 
56
- # Contributing
57
-
58
- This project welcomes contributions and suggestions. Most contributions require you to agree to a
59
- Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
60
- the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
61
-
62
- When you submit a pull request, a CLA bot will automatically determine whether you need to provide
63
- a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions
64
- provided by the bot. You will only need to do this once across all repos using our CLA.
73
+ Take a look at some of the other resources on the website:
65
74
 
66
- This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
67
- For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
68
- contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
75
+ - [Introduction and overview](https://microsoft.github.io/lage/docs/Introduction) of how `lage` works
76
+ - [Tutorial](https://microsoft.github.io/lage/docs/Tutorial/pipeline) about the `pipeline` syntax and other `lage` concepts
77
+ - [CLI reference](https://microsoft.github.io/lage/docs/Reference/cli)
78
+ - [Config reference](https://microsoft.github.io/lage/docs/Reference/config)
79
+ - [Recipes](https://microsoft.github.io/lage/docs/Cookbook/make-jest-fast) for integrating with Jest, ESLint, and more