xpm-js
xpm-js copied to clipboard
xpack
The xPack Project Manager command line tool
When the condition is checked, the package is already installed, and the recommended `--global` fails too.
npm can be configured with something like ``` @codertocat:registry=https://npm.pkg.github.com/ ``` in `.npmrc` or `npm config`. xpm should use these definitions too, and access the correct server.
Run the action after install, before making the folder read/only.
Allow to reinstall dependencies over existing ones. This is particularly useful during development, when using `github:` dependencies, since they no longe require artificial pre-release versions. ``` { "xpack": { "devDependencies":...
Implement multiple profiles to store separate development vs production definitions. The configuration looks like this: ``` { "xpack": { "profiles": { "production": { "devDependencies": { "@micro-os-plus/build-helper": { "specifier": "@micro-os-plus/[email protected]", "local":...
Implement something similar to GitHub Actions `strategy` matrix. ``` "strategy": { "matrix": { "builder": ["cmake", "meson"], "toolchain": ["gcc", "clang"], "buildType": ["debug", "release"] } }, "buildConfigurations: { "test-native-{{ matrix.builder }}-{{ matrix.toolchain...
With more and more packages migrating to ECMAScript modules, xpm needs to be able to use them.
Split the project configuration (now all in `package.json`) and move parts specific to development into separate files. For example: ```json "xpacks": { "devIncludePackageFiles": [ "package-xpm-develop.json", "tests/package-xpm.json" ] } ```
Allow to install in system folders. Search for installed packages will check the home folder first and then the system folders.
## Is your feature request related to a problem? xpm creates a different global directory for every version of an xpack. This makes running and upgrading globally installed binaries difficult....
