You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be useful to have a command to list the actual versions an import map resolves to (behind the alias).
I imagine the command would print an output similar to npm outdated, with the Alias to the left, it's Mapped to version next to it, and the Installed version from package.json to the right.
It should warn if Eik resolves to a lower version than package.json. This validation should give a non-zero exit code so it can be run on CI and cause a build to fail.
The text was updated successfully, but these errors were encountered:
What is Latest in this case? Newest version on Eik? That would be helpful for import map and alias maintainers for sure 👍
I'm looking for a way to give app developers a tool to see if their runtime/client-side dependency will be different from their local/server-side version.
Ok cool. I've added another example to cover that use case then. eik outdated without args would read eik.json/package.json for necessary values, scan import maps being used as well as package.json deps and then lists the table as shown.
It would be useful to have a command to list the actual versions an import map resolves to (behind the alias).
I imagine the command would print an output similar to
npm outdated
, with the Alias to the left, it's Mapped to version next to it, and the Installed version frompackage.json
to the right.It should warn if Eik resolves to a lower version than
package.json
. This validation should give a non-zero exit code so it can be run on CI and cause a build to fail.The text was updated successfully, but these errors were encountered: