@teambit/host-initializer 0.0.743 → 0.0.745
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/agents-template-git.md
CHANGED
|
@@ -101,6 +101,7 @@ bit validate # lint + type-check + tests (fast build)
|
|
|
101
101
|
bit test # run tests only
|
|
102
102
|
bit lint # run linter only
|
|
103
103
|
bit check-types # TypeScript type checker only
|
|
104
|
+
bit ripple <sub-command> # manage Ripple CI jobs on bit.cloud — list/log/errors/retry/stop (jobs that build components in the cloud after export)
|
|
104
105
|
```
|
|
105
106
|
|
|
106
107
|
> **Never run `bit build`** unless absolutely necessary. Always use `bit validate` instead — it's faster and sufficient.
|
|
@@ -245,6 +246,8 @@ git push # push your branch
|
|
|
245
246
|
|
|
246
247
|
> Focus on development workflows: component creation, modification, testing, and local validation. Leave versioning and publishing to CI.
|
|
247
248
|
|
|
249
|
+
Those CI builds run as Ripple CI jobs on bit.cloud. Use `bit ripple list` to see recent jobs, `bit ripple log` to follow one, and `bit ripple errors` to inspect build failures.
|
|
250
|
+
|
|
248
251
|
---
|
|
249
252
|
|
|
250
253
|
## Component Structure
|
package/agents-template.md
CHANGED
|
@@ -99,6 +99,7 @@ bit validate # lint + type-check + tests (fast build)
|
|
|
99
99
|
bit test # run tests only
|
|
100
100
|
bit lint # run linter only
|
|
101
101
|
bit check-types # TypeScript type checker only
|
|
102
|
+
bit ripple <sub-command> # manage Ripple CI jobs on bit.cloud — list/log/errors/retry/stop (jobs that build components in the cloud after export)
|
|
102
103
|
```
|
|
103
104
|
|
|
104
105
|
> **Never run `bit build`** unless absolutely necessary. Always use `bit validate` instead — it's faster and sufficient.
|
|
@@ -236,6 +237,8 @@ bit export # push lane to remote
|
|
|
236
237
|
|
|
237
238
|
> Always run `bit lane create` first. If you're already on a non-main lane, continue using it — don't create a new one.
|
|
238
239
|
|
|
240
|
+
After exporting, components are built in the cloud by Ripple CI. Use `bit ripple log` to follow the current lane's job and `bit ripple errors` to inspect any build failures (or `bit ripple retry` to re-run it).
|
|
241
|
+
|
|
239
242
|
---
|
|
240
243
|
|
|
241
244
|
## Component Structure
|
|
@@ -101,6 +101,7 @@ bit validate # lint + type-check + tests (fast build)
|
|
|
101
101
|
bit test # run tests only
|
|
102
102
|
bit lint # run linter only
|
|
103
103
|
bit check-types # TypeScript type checker only
|
|
104
|
+
bit ripple <sub-command> # manage Ripple CI jobs on bit.cloud — list/log/errors/retry/stop (jobs that build components in the cloud after export)
|
|
104
105
|
```
|
|
105
106
|
|
|
106
107
|
> **Never run `bit build`** unless absolutely necessary. Always use `bit validate` instead — it's faster and sufficient.
|
|
@@ -245,6 +246,8 @@ git push # push your branch
|
|
|
245
246
|
|
|
246
247
|
> Focus on development workflows: component creation, modification, testing, and local validation. Leave versioning and publishing to CI.
|
|
247
248
|
|
|
249
|
+
Those CI builds run as Ripple CI jobs on bit.cloud. Use `bit ripple list` to see recent jobs, `bit ripple log` to follow one, and `bit ripple errors` to inspect build failures.
|
|
250
|
+
|
|
248
251
|
---
|
|
249
252
|
|
|
250
253
|
## Component Structure
|
package/dist/agents-template.md
CHANGED
|
@@ -99,6 +99,7 @@ bit validate # lint + type-check + tests (fast build)
|
|
|
99
99
|
bit test # run tests only
|
|
100
100
|
bit lint # run linter only
|
|
101
101
|
bit check-types # TypeScript type checker only
|
|
102
|
+
bit ripple <sub-command> # manage Ripple CI jobs on bit.cloud — list/log/errors/retry/stop (jobs that build components in the cloud after export)
|
|
102
103
|
```
|
|
103
104
|
|
|
104
105
|
> **Never run `bit build`** unless absolutely necessary. Always use `bit validate` instead — it's faster and sufficient.
|
|
@@ -236,6 +237,8 @@ bit export # push lane to remote
|
|
|
236
237
|
|
|
237
238
|
> Always run `bit lane create` first. If you're already on a non-main lane, continue using it — don't create a new one.
|
|
238
239
|
|
|
240
|
+
After exporting, components are built in the cloud by Ripple CI. Use `bit ripple log` to follow the current lane's job and `bit ripple errors` to inspect any build failures (or `bit ripple retry` to re-run it).
|
|
241
|
+
|
|
239
242
|
---
|
|
240
243
|
|
|
241
244
|
## Component Structure
|
package/package.json
CHANGED
|
@@ -1,12 +1,12 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@teambit/host-initializer",
|
|
3
|
-
"version": "0.0.
|
|
3
|
+
"version": "0.0.745",
|
|
4
4
|
"homepage": "https://bit.cloud/teambit/harmony/host-initializer",
|
|
5
5
|
"main": "dist/index.js",
|
|
6
6
|
"componentId": {
|
|
7
7
|
"scope": "teambit.harmony",
|
|
8
8
|
"name": "host-initializer",
|
|
9
|
-
"version": "0.0.
|
|
9
|
+
"version": "0.0.745"
|
|
10
10
|
},
|
|
11
11
|
"dependencies": {
|
|
12
12
|
"lodash": "4.17.21",
|
|
@@ -31,7 +31,7 @@
|
|
|
31
31
|
"@teambit/config-store": "0.0.223",
|
|
32
32
|
"@teambit/legacy.constants": "0.0.31",
|
|
33
33
|
"@teambit/legacy.scope-api": "0.0.185",
|
|
34
|
-
"@teambit/objects": "0.0.
|
|
34
|
+
"@teambit/objects": "0.0.539"
|
|
35
35
|
},
|
|
36
36
|
"devDependencies": {
|
|
37
37
|
"@types/lodash": "4.14.165",
|
|
File without changes
|