If your application is using projects with dependencies hosted in private npm scopes, you can deploy such with - true to our style - just one command (and a flag):
This command will forward your npm credentials during the build process to fetch the required modules. Here's a little video of this feature in action, using a scoped private module in
If want to forward your npm
credentials every time you create a new deployment using now, you can set the
property inside your global
You can read more about how to configure Now
to your needs here
makes it so radically easy to manage your organization's code. Sharing lots of small modules that do one thing well can make your team vastly more productive and your code easier to maintain and iterate on.
We're committed to giving you the best experience when deploying as an individual or in a team, and we hope this feature enhances that.
flag, nor the
config property support npm's enterprise plans
or packages hosted on a custom infrastructure at the moment. But don't worry, we're already working on it!