Private Spree NPM Modules
This is the place where we are doing our POC for Spree private npm modules
Why a Private Registry?
With so many repos in our arsenal, there is a lot of code-duplication and often work-duplication taking place because we don't have a solid way to share code between repos. Since most of our work is on node-driven services, NPM seems like the natural answer until you see what npmjs charges for keeping the public out of your code. It also means we trust them too with our proprietary code. Hence our own private npm registry.
Private Repository Location
Don't have an Account?
PM @trent or @markh with an account request along with requested username
and password. Keep in mind that this is a public-facing interface and contains
proprietary software, so password123 is not going to fly.
How to get NPM to see it?
npm login --reg https://npm.spreeza.net --scope @spree
You will be prompted for a username, password and email address. Once you've
provided this an entry will be made into your ~/.npmrc file to indicate the
credentials to use against the correct registry when you install packages in
the form @spree/modulename
Why the Spree Folder?
For now we only have a @spree organizational designation for modules that are
private to spree. Later on we may want to introduce other organizational
designations and to avoid moving large numbers of files around in git, the
spree folder offers a way to future-proof.
It should really have been
@spree but for some reason git loses it's lunch when you start a folder with
an @