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
By default, npm will not install new versions of a template because it finds it's already installed and skips the installation process. This is a good thing in most cases but can create confusion when someone is trying to use a template and they don't get the latest version features and fixes.
Users can overcome this by executing something like:
ag asyncapi.yml @asyncapi/html-template@latest -o output
# Notice the `@latest`
But that's something you do when you really know how the Generator works.
Description
I suggest we add a console.info indicating that a template has a new version available. Something like:
This template has a newer version and you can safely update.
Use `@asyncapi/html-template@latest` as your template name to install the latest version.
Example:
ag asyncapi.yml @asyncapi/html-template@latest -o output
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with detailed explanation.
Thank you for your contributions ❤️
This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.
There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.
Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.
Reason/Context
By default, npm will not install new versions of a template because it finds it's already installed and skips the installation process. This is a good thing in most cases but can create confusion when someone is trying to use a template and they don't get the latest version features and fixes.
Users can overcome this by executing something like:
ag asyncapi.yml @asyncapi/html-template@latest -o output # Notice the `@latest`
But that's something you do when you really know how the Generator works.
Description
I suggest we add a console.info indicating that a template has a new version available. Something like:
The text was updated successfully, but these errors were encountered: