-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes Not Updating in Development Mode #21
Comments
Interesting. Are you seeing anything logged to your console when you save a .html or .js file? When you save a .html file, a big packet should be written out with all the new templates in it. When you save a .js file, the server should automatically restart. What OS and version of Node are you running? |
Nothing is being logged to my console after saving a .html or .js file. Something else: Without defining NODE_ENV=development in my .bash_profile, Derby outputs: Mac OS X 10.7.3 and Node.js 0.6.14. |
Are you using the default directory structure? The watch code only looks in the root directory of your project. On line 128 of |
Ok, then this is caused on my end. I am religiously opposed to abbreviations and renamed every instance of |
I still had issues until 0.3.0. I'm happy to report all works now as expected. |
Sweet! Glad it got fixed. |
In development mode, without restarting Derby, changes made to any .js or .html file do not display in the browser. Changes to .styl files seem to work as expected.
I have in my .bash_profile:
export NODE_ENV=development
andStarting cluster with 1 workers in development mode
in my console after starting Derby.I am using the latest Derby: 0.1.10 on port 8080 and browsing with latest production Chrome.
The text was updated successfully, but these errors were encountered: