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
I'm using a Nuxt layer with the GitHub repo approach which lacks the versioning we would get if it were a npm package.
Hence I want to make sure that I'm using the latest layer commit and otherwise fail to catch bugs as early as possible.
Currently, If I set any incorrect GIGET_AUTH env (Repo is private) it doesn't throw an error and uses the currently folder in node_modules.
A flag that throws an error and/or warning if fetching the repo fails would be great! Thanks a lot!
Additional information
Would you be willing to help implement this feature?
The text was updated successfully, but these errors were encountered:
Describe the feature
Hello 👋
I'm using a Nuxt layer with the GitHub repo approach which lacks the versioning we would get if it were a npm package.
Hence I want to make sure that I'm using the latest layer commit and otherwise fail to catch bugs as early as possible.
Currently, If I set any incorrect
GIGET_AUTH
env (Repo is private) it doesn't throw an error and uses the currently folder innode_modules
.A flag that throws an error and/or warning if fetching the repo fails would be great! Thanks a lot!
Additional information
The text was updated successfully, but these errors were encountered: