Skip to content
This repository has been archived by the owner on Aug 30, 2021. It is now read-only.

node-inspector as optionalDependencies #1700

Closed
prashanthmadi opened this issue Jan 13, 2017 · 2 comments
Closed

node-inspector as optionalDependencies #1700

prashanthmadi opened this issue Jan 13, 2017 · 2 comments

Comments

@prashanthmadi
Copy link

Build fails in azure web apps because of node-gyp issue. Is it possible to make node-inspector as optional dependency ?

@prashanthmadi prashanthmadi changed the title can we make node-inspector optionalDependencies node-inspector optionalDependencies Jan 13, 2017
@prashanthmadi prashanthmadi changed the title node-inspector optionalDependencies node-inspector as optionalDependencies Jan 13, 2017
@prashanthmadi
Copy link
Author

prashanthmadi commented Jan 13, 2017

If anyone is looking for deploying meanjs on azure web apps.

I made a fork of this at below link which works in azure web app. Fork might be temporary and would be deleted.
https://github.com/prashanthmadi/mean

  1. nodemon doesn't work on azure web apps (It might not be a best practice to use nodemon for prod apps)
  2. Lock nodejs version in package.json
  3. make node-inspector as optionalDependencies (node-gyp failure issue)

Blog :
Running Mean.js App on Azure App Services with Continuous Delivery Integration https://prmadi.com/running-mean-js-app-on-azure-app-services/

@lirantal
Copy link
Member

lirantal commented Apr 8, 2017

Thanks @prashanthmadi
#1744 fixes the issue now, merged to master already.

@lirantal lirantal closed this as completed Apr 8, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants