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
When trying to follow along with the tutorials, the hs init command wasn’t working for me. It turns out that the hs command was already globally taken by http-server.
I make it a point not to install global npm scripts generally, but both @hubspot/cli and http-server are the sorts of packages that could make sense to have together in the global namespace.
http-server has actually already implemented a change to remove the hs alias from their script by default, so upgrading it and reinstalling @hubspot/cli sufficed. However, I think that hubspot should be aware of this possibility and also adopt the approach of using a longer, more unique, less-likely-to-conflict namespace (like hubspot) and allow end-users to alias it with shorter commands if desired.
Cleary a change like that will need to happen over multiple versions of the package. In the meantime, I do suggest aliasing hubspot so that it can be used instead in instances of conflict.
The text was updated successfully, but these errors were encountered:
Description and Context
When trying to follow along with the tutorials, the
hs init
command wasn’t working for me. It turns out that thehs
command was already globally taken by http-server.I make it a point not to install global npm scripts generally, but both @hubspot/cli and http-server are the sorts of packages that could make sense to have together in the global namespace.
http-server
has actually already implemented a change to remove thehs
alias from their script by default, so upgrading it and reinstalling @hubspot/cli sufficed. However, I think that hubspot should be aware of this possibility and also adopt the approach of using a longer, more unique, less-likely-to-conflict namespace (likehubspot
) and allow end-users to alias it with shorter commands if desired.Cleary a change like that will need to happen over multiple versions of the package. In the meantime, I do suggest aliasing
hubspot
so that it can be used instead in instances of conflict.The text was updated successfully, but these errors were encountered: