config not sufficient for compiled css frameworks about meteor-bower HOT 2 CLOSED

I wonder how many bower packages are in this situation. Bower is supposed to be a client side package manager, so files listed in the "main" field should be compiled in html/js/css/assets because other file extensions such as .coffee or .scss aren't supported on the browser.

In this case I guess we don't want to compile all scss files in one big css, but instead we want to include mixins in our own scss files and then compile it in css on the server side. So bower doesn't appear as a good client for this job:

Why not create an atmosphere package that will:

• rely on the NPM sass package for the compilation
• include the bootstrap-sass repository as a git submodule
• manually add js and assets with the package.js API

BTW it's not possible (yet?) to include in the bundle a scss, a coffee or even a html file. The current API allows only: addJavascript, addStylesheet and addAsset see here.

So automatic bundling of this package doesn't seem feasible in the current state of both meteor and bower APIs.

from meteor-bower.

Thanks for the thoughtful response. This may just be a "won't fix" issue, and I won't be offended if you just close with no action.

It's the build step that is the killer. I guess I would agree that including bootstrap.scss in main is a mistake on Twitter's part - it has to be compiled to use it even though it is a client side library, whereas it seems like main is for files that should be loaded directly by the browser. If we are going to add config, perhaps it makes more sense to let a smart package be the recipient of that since it can manage build, client, and server. Anyway, thanks for taking the time to think about this. :-)

from meteor-bower.