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,
I'm looking at this https://github.com/marko-js/examples/tree/master/examples/library and it's looking like a great foundation to build my component library on, but I don't know where to go from here. How should we use these components in another Marko Run app for example?
@ancashoria you can publish Marko packages like any other npm package. If it's based on the library example, everything is publish ready. You just need to npm run build first, eg npm run build && npm publish (or whatever publishing pipeline you have to npm).
We personally like using https://github.com/changesets/changesets for managing releases / changelogs, but any tool to publish to npm should work fine as long as build happens first.
Activity
DylanPiercey commentedon Mar 22, 2026
@ancashoria we've got this section here about how tags are discovered (and specifically how tags from node_modules are discovered). Is this what you're looking for?
https://markojs.com/docs/reference/custom-tag#installed-custom-tags
ancashoria commentedon Mar 22, 2026
That's really helpful, now I just need to look into how to publish or link the library to the consuming marko project.
Thanks
DylanPiercey commentedon Mar 22, 2026
@ancashoria you can publish Marko packages like any other
npmpackage. If it's based on thelibraryexample, everything is publish ready. You just need tonpm run buildfirst, egnpm run build && npm publish(or whatever publishing pipeline you have to npm).We personally like using https://github.com/changesets/changesets for managing releases / changelogs, but any tool to publish to
npmshould work fine as long asbuildhappens first.