node package manager
Stop wasting time. Easily manage code sharing in your team. Create a free org »



  • For more information regarding alpine-logging

In alpine-logging Update config.js to test: Add:

process.env.FORCE_CLIENTID = 'get-from-config.js-file';
process.env.FORCE_CLIENTSECRET = 'get-from-config.js-file';
process.env.FORCE_REDIRECTURI = 'http://localhost:3000/oauth/_callback';
process.env.FORCE_APIVERSION = 'v28.0';
//process.env.MIXPANEL_ID = 'get-from-config.js-file';


exports.envSupportsAnalytics = false; //process.env.MIXPANEL_ID && process.env.FORCE_CLIENTID  && process.env.FORCE_REDIRECTURI  && process.env.FORCE_APIVERSION && process.env.FORCE_CLIENTSECRET;
exports.envSupportsLogging = true; //process.env.FORCE_CLIENTID  && process.env.FORCE_REDIRECTURI  && process.env.FORCE_APIVERSION && process.env.FORCE_CLIENTSECRET;

Make code changes

  • !!! modify version before commiting/publishing...
  • Commit
  • Push
  • Submit pull request
    • Do we need to wait for PR to go thru before publishing?
  • npm publish .
    • !!! modify version before publishing...
    • If you haven’t already, add yourself as an NPM user (only need to do this once)
    • npm adduser (and follow the prompts)
    • Have owner add you as an owner: (verify owner with: npm owner ls alpine-logging )
    • npm owner add alpine-analytics

In alping-mobile

  • mimosa clean
  • update package.json with new version
  • npm install
    • verify change in node_modules