1

I was able to get live edit working following these instructions: running-and-debugging-node-js

And I was able to get nodemon running following this post: How can I run nodemon from within WebStorm?

However, I am unable to combine the two configurations to get live edit working with nodemon...

If I add nodemon parameters to my live edit config it stops working

ideas?

Thanks

Community
  • 1
  • 1
Dustin Jackson
  • 377
  • 4
  • 13

2 Answers2

3

Works fine for me (WebStorm 7.0.1). here is my nodemon run configuration (I'm on Windows 7):

**Configuration tab**

Working directory: my project dir

JavaScript file: ~\AppData\Roaming\npm\node_modules\nodemon\nodemon.js

Application parameters: app.js

**Browser/LiveEdit tab**

'After launch' checked

'with javascript debugger' checked

http://localhost:3000/index.html

Whe I run this configuration in debugger, all changes made to html/css (served using connect.static) are 'live'

If similar configuration doesn't work for you, can you provide a sample project that shows up your problem?

lena
  • 90,154
  • 11
  • 145
  • 150
  • hmm.. I'm still new to WebStorm, but I was able to get it working by launching each debugging session separately. I created a config for Nodemon, launch the session, and then create a config for Live-Edit and launched that as well. Now if I make a change to a js file nodemon will restart, and editing my jade files is live. Pretty awesome ! – Dustin Jackson Nov 13 '13 at 15:26
  • @Dustin, You shouldn't have to create new debugging sessions each time you want the live to update. I'm running nodemon in Webstorm 10.0.3. What happens for me is I go to my jade template, change some of the markup, and my existing debug session refreshes the browser automatically. I make the change then I toggle back to Chrome and it refreshes itself! That's the experience you should be seeing. – PositiveGuy Jun 09 '15 at 16:12
  • @Dustin, make sure you have added nodemon to your package.json definintion. If you didn't install nodemon with the --save option which would have added that entry to your package.json for you, you'll need to manually add that to your dev dependencies – PositiveGuy Jun 09 '15 at 16:13
0

Do you have nodemon added to your package.json?

"devDependencies": {
  "nodemon": "~1.3.7"
},

or did you install nodemon with the --dev flag which would have added that for you? e.g. install nodemon --dev

josliber
  • 43,891
  • 12
  • 98
  • 133
PositiveGuy
  • 17,621
  • 26
  • 79
  • 138