# 🎇 FlexDash alpha release - round 2

**URL:** <https://discourse.nodered.org/t/flexdash-alpha-release-round-2/67783>\
**Category:** Share Your Nodes\
**Tags:** flexdash\
**Created:** [16 September 2022 04:14 UTC](https://discourse.nodered.org/t/flexdash-alpha-release-round-2/67783 "2022-09-16T04:14:30Z")\
**Posts on this page:** 1\
**Showing post:** 104

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [11 December 2022 10:26 UTC](https://discourse.nodered.org/t/flexdash-alpha-release-round-2/67783/104 "2022-12-11T10:26:16Z")

</div>

Hi @tve

you can always give your beta / testing versions tags like 0.4.125-beta or -test etc... so they are not "latest"...

And then also in npm you can publish them like that also - `npm publish --tag test`

see [Adding dist-tags to packages | npm Docs](https://docs.npmjs.com/adding-dist-tags-to-packages)

That stops a generic `npm i your package` just picking it up - but someone can install it using the correct tag. You can also just run `npm pack` locally which will give you a .tgz file to install locally using npm.

Of course they could also install direct from github (if the compiled/fully packaged code is there) which means you don't have to "pollute" npm at all. This is what Bart does for a lot of his test packages - eg see [Announce node-red-contrib-http-logger](https://discourse.nodered.org/t/announce-node-red-contrib-http-logger/4178)

---

_[View the full topic](https://discourse.nodered.org/t/flexdash-alpha-release-round-2/67783)._