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
Hi @mahaoming, thanks for opening up this issue and asking about this. It's a good question that I think depends on the type of package you're building. I say this because you could use packages in different ways, such as a dependency in a project or as a CLI tool. With that in mind, a dev script would vary based on what you need the output to be and how you'll use it while developing.
I haven't personally had a lot of experience building CLI tool packages, and I have had more experience building standard packages. In that case, my development workflow would typically result in me running npm link in the directory of the package I'm building, and then, in a separate project I want to test it out in, running npm link <name-of-the-package>.
Does that help a bit? If not, let me know some more specifics on what you're looking to do, and I'll do my best to help.
@mahaoming any chance you've had a moment to review my response yet? Let me know if you have further details to share or if we can close out this issue. Thanks
Hey @mahaoming checking one more time before closing the issue. Have you had a chance to review my prior response and see if that helps? Let me know when you do please. The issue will be automatically closed if no further response is found in 2 weeks
Is there an existing feature request for this?
Description
how to use dev
Is that right?
Additional Information
No response
The text was updated successfully, but these errors were encountered: