Closed tuxuser closed 2 years ago
Two cents. Considering how flaky unpinned npm installs can be, I would suggest:
npm install
once to create package-lock.json
package-lock.json
. This is what we want - this will pin down to very specific version of ares-cli, but also its transitive dependencies - I am not entirely sure how npm-shrinkwrap.json
(which is an alternative name for package-lock.json
) contained in ares-cli affects npm behaviour, but better safe than sorry.npm install -g
(without specifying package name) executed in main project directory in CI - this should install all dependencies of a local package globally (respecting our pins in package-lock.json
)
Hi!
Overview of this PR:
Bonus:
NOTE: The npm dependency
webosose/ares-cli
allows a standalone / non-SDK build process and almost eliminates the need for the full blown WebOS SDK to be installed.Almost because it's missing two ares-tools:
Duplicated files inside ipk
IPK content before refactoring:
IPK content after
Cleanup repo structure
The repository contains the "master" package.json file in its root, a service-only package.json file is located inside
services/
. Also,webosose/ares-cli
is now listed as a dependency so the project can be built without webos SDK being installed.README
README is updated with instructions on how to use npm for building.