You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,7 @@ $ npm run build
47
47
48
48
***Many Flavors:** We like to be together not the same, that’s why create-cycle-app comes with 4 core flavors that you can mix and match with your favorite reactive stream library. Furthermore, a discovery mechanism allows to find and use any flavor published on the npm registry. Alternatively, you can use your own flavors from any registry such as GitHub or your own.
49
49
50
-
***No Lock-In:** Specifically made for beginners and to provide fast bootstrap for new projects, create-cycle-app doesn't have the ambition to be __the__ tool for working with Cycle.js projects. With that in mind, it's easy to leave `create-cycle-app` defaults and follow your own steps, by running `npm run take-off-training-wheels`.
50
+
***No Lock-In:** Specifically made for beginners and to provide fast bootstrap for new projects, create-cycle-app doesn't have the ambition to be __the__ tool for working with Cycle.js projects. With that in mind, it's easy to leave `create-cycle-app` defaults and follow your own steps, by running `npm run eject`.
51
51
52
52
## Why Use This?
53
53
@@ -113,7 +113,7 @@ Run the default test tool.
113
113
114
114
Generate a production-ready build content, on the build folder (this folder is gitignored)
115
115
116
-
### `npm run take-off-training-wheels`
116
+
### `npm run eject`
117
117
118
118
Copy dependencies and configurations to the project folder, update package.json and remove the dependency on the flavored cycle-scripts.
119
119
@@ -176,7 +176,7 @@ Take a look at [cycle-scripts-es-browserify](./cycle-scripts-es-browserify) as a
176
176
│ ├── build.js
177
177
│ ├── init.js
178
178
│ ├── start.js
179
-
│ ├── take-off-training-wheels.js
179
+
│ ├── eject.js
180
180
│ └── test.js
181
181
└── template
182
182
├── gitignore
@@ -195,7 +195,7 @@ Take a look at [cycle-scripts-es-browserify](./cycle-scripts-es-browserify) as a
195
195
196
196
`index.js` is the entry point for each command exposed to the target project. It could be really simple, just calling the next script file without ceremony.
197
197
198
-
`scripts/` directory holds each script used in the project. The `start.js` script is used to start a development server. `test.js`, as the name suggests, call the test tool. `build.js` is used to bundle the target project to a deliverable set of files, production-ready. `take-off-training-wheels.js` is mostly a copy-and-paste tool, that adapts the target project to reproduce the same commands from the flavor. Last, but not least, `init.js` is the script called by `create-cycle-app` command, in order to install development dependencies and copy initial files.
198
+
`scripts/` directory holds each script used in the project. The `start.js` script is used to start a development server. `test.js`, as the name suggests, call the test tool. `build.js` is used to bundle the target project to a deliverable set of files, production-ready. `eject.js` is mostly a copy-and-paste tool, that adapts the target project to reproduce the same commands from the flavor. Last, but not least, `init.js` is the script called by `create-cycle-app` command, in order to install development dependencies and copy initial files.
199
199
200
200
`templates/` directory holds template files for the target project. This is optional, and unlike other files, could have any structure you desire.
0 commit comments