Skip to content
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

disabled: no longer #5

Open
say2joe opened this issue Oct 21, 2013 · 1 comment
Open

disabled: no longer #5

say2joe opened this issue Oct 21, 2013 · 1 comment

Comments

@say2joe
Copy link

say2joe commented Oct 21, 2013

Please update your instructions appropriately for Brackets 32. There is no longer a disabled folder. That aside, I'm not sure that would be the best was to manage a local repo if its separate on GitHub... should probably just create an extra link. Here's the caveat -- how to do this simply on a PC.

@nmn
Copy link

nmn commented Nov 9, 2013

@say2joe I'm on sprint 33, and there is a disabled folder, I'm on a mac though.
you should look for it here:

C:\Users\<user>\AppData\Roaming\Brackets\extensions\disabled

In case you can't find it, you can just use the users folder.

Also the instructions are identical for the newest sprint, And I tested it and it mostly worked. (I added a console.log which worked without restarting node. But I added a new express route and that didn't just work without restarting the node server. Also in the large scheme of things I saw no benefit to using it over something like supervisor or forever or nodemon.

If you want to use it though you can try this:
https://groups.google.com/forum/#!searchin/brackets-dev/node.js/brackets-dev/6YQFKKCqXtc/G0C_6ZLY26gJ

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants