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

Can I change the root path for compilation? #327

Open
charlievaughan-zz opened this issue Oct 21, 2016 · 0 comments
Open

Can I change the root path for compilation? #327

charlievaughan-zz opened this issue Oct 21, 2016 · 0 comments

Comments

@charlievaughan-zz
Copy link

We are using LESS with Adobe Experience Manager (AEM) which will compile the LESS files when they are pushed into a local instance (which is the normal way of doing things).

But with AEM you have little visibility of whether the AEM LESS compiler has thrown an error due to invalid LESS.

So we want to compile a copy of our less outside AEM as part of a Grunt pipeline just to keep an eye on LESS compilation issues as they occur.

The issue is with the paths used to import LESS style-sheets which are like so:

@import "/etc/designs/pdc/clientlibs_base/css/global/imports.less";

Meanwhile Grunt is run from the root directory which would require the import paths to be:

root/app/jcr_root/etc/designs/pdc/clientlibs_base/css/global/imports.less

So while the paths used to import the LESS files all work fine once pushed into AEM, they error when compiled from the root directory.

So the question is how we could go about configuring grunt-contrib-less to use a relative path or technique to compile from the root directory?

There seems to be several options that can be configured that might solve our issue, but without some examples its difficult to tell.

Thanks for your help

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

1 participant