|
| 1 | +## Description |
| 2 | + |
| 3 | +This project is implementing [TodoMVC](https://github.com/tastejs/todomvc) in React and Kotlin. |
| 4 | +This project was bootstrapped with [Create React Kotlin App](https://github.com/JetBrains/create-react-kotlin-app). |
| 5 | + |
| 6 | +Below you will find some useful information on how to work with this application.<br> |
| 7 | +We're still working on this guide and you can find its most recent version [here](https://github.com/JetBrains/create-react-kotlin-app/blob/master/packages/react-scripts/template/README.md). |
| 8 | + |
| 9 | + |
| 10 | +## Available Scripts |
| 11 | + |
| 12 | +Once the installation (after `npm install`) is done, you can run some commands inside the project folder: |
| 13 | + |
| 14 | +### `npm start` or `yarn start` |
| 15 | + |
| 16 | +Runs the app in development mode.<br> |
| 17 | +Open [http://localhost:3000](http://localhost:3000) to view it in the browser. |
| 18 | + |
| 19 | +The page will reload automatically when you make edits.<br> |
| 20 | +You will see build errors and lint warnings in the console. |
| 21 | + |
| 22 | +### `npm run build` or `yarn build` |
| 23 | + |
| 24 | +Builds the app for production to the `build` folder.<br> |
| 25 | +It ensures that React is bundled in production mode and the build is optimized for best performance. |
| 26 | + |
| 27 | +The build is minified and the filenames include hashes for cache management. Your app is ready to be deployed. |
| 28 | + |
| 29 | +### `npm run eject` |
| 30 | + |
| 31 | +**Note: this is a one-way operation. Once you `eject`, you can’t go back!** |
| 32 | + |
| 33 | +If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project. |
| 34 | + |
| 35 | +Running `npm run eject` copies all configuration files and transitive dependencies (webpack, Kotlin Compiler, etc) right into your project so you have full control over them. Commands like `npm start` and `npm run build` will still work, but they will point to the copied scripts so you can tweak them. At this point, you’re on your own. |
| 36 | + |
| 37 | +## Debugging the App |
| 38 | + |
| 39 | +You can debug the running app right in IntelliJ IDEA Ultimate using its built-in JavaScript debugger. The IDE will run a new instance of Chrome and attach a debugger to it. |
| 40 | + |
| 41 | +Start your app by running `npm start`. Put the breakpoints in your Kolin code. |
| 42 | +Then select `Debug in Chrome` from the list of run/debug configurations on the top-right and click the green debug icon or press `^D` on macOS or `F9` on Windows and Linux to start debugging. |
| 43 | + |
| 44 | +Currently, debugging is supported only in IntelliJ IDEA Ultimate 2017.3. |
| 45 | + |
| 46 | +You can also debug your application using the developer tools in your browser. |
| 47 | + |
0 commit comments