locktrip-svc-layer v1.0.54
In Short
Developing Flow
(short version)
1. git pull/checkout
(clean checkout, no nodemodules)
2. npm install
3. Make changes
4. Build - run npm run ES6-to-ES5
(_lib folder will be updated)
5. Test (with Centralized-App - see the Developing Flow In Detail below)
6. Commit and push your changes
Releasing Flow
(short version)
1. Make sure all changes are committed (step 6. in Developing Flow)
2. npm version patch|minor|major|...
(this creates a tag and commits it - without pushing it)
3. Push the version change and the new generated tag
In Detail
Developing Flow
- Make sure you have a clean checkout and no node_modules/ (delete it if present)
- Get dependencies with
npm install
- Make your changes
- Build - run
npm run ES6-to-ES5
(lib folder will be updated) Test by following these steps:
- copy the current working Service-Layer folder into Centralized-App/node_modules/locktrip-svc-layer
run Centralized-App and make sure your changes working as expected
NOTE: Alternatively you can directly checkout and work in the Centralized-App/node_modules/locktrip-svc-layer/ folder - but you have to know what you are doing. For examlpe running
npm install
could delete node_modules/locktrip-svc-layer/ and your canges would be lost if you hadn't committed your changes before runningnpm install
.
Push changes to Service-Layer GitHub. This should contain both changes in src/ and lib/ folders as well as any package.json package-lock.json files.
Releasing Flow
- Make sure all code is pushed to Service-Layer on GitHub (step 6. in Developing Flow)
- Run
npm version patch
to update version (or whatever other nedednpm version
alternative - minor, major etc.). - Push the version change and tag (created by
npm version ...
command in previous step 2.)