# Add npm publish action

**URL:** https://www.finalbuilder.com/forums/t/add-npm-publish-action/5497
**Category:** Feature Requests
**Tags:** implemented
**Created:** [August 3, 2016, 12:11pm UTC](https://www.finalbuilder.com/forums/t/add-npm-publish-action/5497 "2016-08-03T12:11:18Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![catenalogic](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/catenalogic/32/116_2.png) [@catenalogic](https://www.finalbuilder.com/forums/u/catenalogic)
#### Post date: [August 3, 2016, 12:11pm UTC](https://www.finalbuilder.com/forums/t/add-npm-publish-action/5497/1 "2016-08-03T12:11:18Z")

</div>

We are creating npm packages using Continua CI (to automate building our client side web components). In the deploy step, we would need an npm publish to publish it to a registry (in our case MyGet).  
  
Here are some docs:  
  
[http://docs.myget.org/docs/reference/myget-npm-support](http://docs.myget.org/docs/reference/myget-npm-support)  
  
I think this is the command really needed (the adduser only has to be done once):

```
npm publish  –registry=https://www.myget.org/F/your-feed-name/npm
```

We will probably use pre-authenticated urls in order to deal with authentication anyway.  
  
Thanks!

---

<div class="post-metadata">

### Author: ![Sparky](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/sparky/32/10_2.png) [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)
#### Post date: [August 4, 2016, 6:24am UTC](https://www.finalbuilder.com/forums/t/add-npm-publish-action/5497/2 "2016-08-04T06:24:53Z")

</div>

Hi Geert,  
  
Yes, we’re on to it already. &nbsp;Expect an npm publish action in the next couple of releases.