This looks good, but I think, at least for now, we need to always show some sort of warning when --include-std is not used.

We have already had one issue opened #92 where the fact that the standard library did not get installed (even though it's a transitive dependency) led to confusion.

The message can be much shorter in this case, and I would propose simply always printing it for any command that involves installing dependencies.

Once this behaviour is either standardised or widely understood we can remove the message.

This looks good, but I think, at least for now, we need to always show some sort of warning when --include-std is not used.

This PR does always print the warning, except for the lock command.

This looks good, but I think, at least for now, we need to always show some sort of warning when --include-std is not used.

This PR does always print the warning, except for the lock command.

$ sysand env install "urn:kpar:sysmod"
     Syncing env
  Installing urn:kpar:sysmod 5.0.0-alpha.2
$

says nothing about not installing stdlib dependencies, even though they are explicit dependencies of sysmod (this is precisely the case that confused the user in the ticket above).

It does:

$ sysand env install 'urn:kpar:systems-library'`
warning: SysML/KerML standard library package 'urn:kpar:systems-library'
         is ignored, as it should always be provided by your tooling.
         If you want to process it, pass the '--include-std' flag
     Syncing env
env is up to date

(it shouldn't sync the env if packages didn't change, will fix that)

It does:

$ sysand env install 'urn:kpar:systems-library'`
warning: SysML/KerML standard library package 'urn:kpar:systems-library'
         is ignored, as it should always be provided by your tooling.
         If you want to process it, pass the '--include-std' flag
     Syncing env
env is up to date

(it shouldn't sync the env if packages didn't change, will fix that)

When explicitly trying to install a standard library project yes, but not if that standard library project is only a (transitive) dependency, which will effectively be almost every project.

Sorry, my bad. I meant to check with urn:kpar:sysmod, but somehow forgot.

Fixed:

sysand env install 'urn:kpar:sysmod'
warning: Direct or transitive usages of SysML/KerML standard library packages are
         ignored by default. If you want to process them, pass `--include-std` flag
     Syncing env
  Installing urn:kpar:sysmod 5.0.0-alpha.2

Also shortened the warning messages and made them more specific.
Fixed npm tests by installing dev deps with npm install. No idea why they were working in CI before, probably CI works diferently from bindings/js/scripts/run_tests.sh.