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
Random fixes required when I first checked out the project. #105
Conversation
…m pulled in for the project.
…n (coffee is to fast sometimes)
…t the `lib` dir is created.
Actually the redis dependency is optional... And if the system wide coffee matches the required version it won't be installed locally. It would be better to define a PATH that includes the node_modules here as well as the normal path and just call coffee. That way the shell will use the first one it finds. |
iPhone button booboo |
I will torch the redis thing, it must just be the sharejs example that requires it. Also, I will look into the PATH extension idea (pretty sweet to know if that works as I can use it on some other projects). |
…in` to PATH so that calls will all work.
@wmertens Updated to fix the issues you found. |
Ideally just uses the prepublish, and not postinstall. Coffee should be moved as a dev dep only. It shouldn't be needed to run the server. |
1 similar comment
Ideally just uses the prepublish, and not postinstall. Coffee should be moved as a dev dep only. It shouldn't be needed to run the server. |
@wmertens the lib directory already isn't part of git. The package's root in npm is index.js, which looks like this: require('coffee-script');
module.exports = require('./src'); This means The lib directory is only used for two purposes:
|
So should the postinstall "cake build" be removed and the prepublish have "cake webclient"? |
Random fixes required when I first checked out the project.
Thanks! |
Build is broken. |
Yup - it's because of sockjs, it broke as soon as I updated webclient a couple commits later. I have something that no longer breaks the tests but lets them last forever. I'm getting closer :-) |
The only thing I see that could be problematic (through my naive eyes) would be the
redis
package as a dependency. In order to run the project redis is required so it seemed that this needed to be there.Otherwise, this ensures that cake uses the projects coffee executable instead of the system wide one and adds some hooks to ensure the lib directory is up to date at crucial points.