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

How can we use asset pipeline library with jsblocks server. #142

Open
chardy opened this issue Apr 28, 2016 · 3 comments
Open

How can we use asset pipeline library with jsblocks server. #142

chardy opened this issue Apr 28, 2016 · 3 comments

Comments

@chardy
Copy link

chardy commented Apr 28, 2016

Hi,

Could we use this: https://github.com/adunkman/connect-assets with jsblocks server?

Or https://github.com/nodeca/mincer ? Any other alternatives?

Could you give me the example to do that?

Thanks.

@Kanaye
Copy link
Collaborator

Kanaye commented Apr 28, 2016

Hey @chardy.
I'm sorry to say, but currently you can't.
Css/Client side resources might be possible (I'm not sure how express.static handles caching) through a watching build system like grunt or gulp. But with js/html it's currently not possible. Jsblocks will cache the code itself even if (cache: false) (will only reexecute the "known" code) is set.
Maybe could an option debugging could be added that would register an fs.watcher for the app that clears the caches if a file changes. So a normal build system could be used for the app.

What do you think?

@chardy
Copy link
Author

chardy commented Apr 28, 2016

I am currently using ruby on rails with jsblocks. The only issue with that is the "back history" button is not working. I think I mentioned that before. Thats why I am moving my client to jsblocks server. But now, another issue is the difficulty integrating it with mincer.

@Kanaye
Copy link
Collaborator

Kanaye commented Apr 29, 2016

I'm not sure if migrating something to blocks serverside rendering is the best decision right now, as it's not nearly feature complete and has some issues.
I couldn't reproduce your issue with the "back history" you mentioned in #137.

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

No branches or pull requests

2 participants