Import Each Less File Only Once

[michael-savory]

This is somewhat a duplicate of issue #49, however I did not find any clarification on what the best strategy was. Also, I should mention that I'm doing all of my compiling on the server side using node.

Here is my problem.

home.less:

@import "config";

@import "reset";

@import "core";

@import "base";

How I would like this to work is that it's like I'm specifying all of my dependencies at the top of my less file, and it will get compiled down into one nice css file.

However, what you get instead is:

-- config.css

-- reset.css

-- config.css

-- core.css

-- config.css

-- core.css

-- base.css

-- home.css

Basically, everyone depends on "config", because that's where all my colors and functions are located, and it would be nice if that was only loaded only once. Notice, in my specific case "core" gets loaded twice as well.

Is there a workaround, a hack, an alternative, or a fork that deals with this scenario. I feel like it's valuable from the standpoint that you could have css files like the following:

home.css

index.css

posts.css

blogs.css

And these would more or less dynamically create themselves with only the necessary css components based upon the imports you specify.

Cheers.

[minipai]

I would like this feature request too. SASS wont compile .scss files start with '_' such like _config.scss.

[lukeapage]

@import-once is implemented

[jreading]

Import once test fails, are we sure this is resolved?

[lukeapage]

its implemented and there is another bug about it not working, now it is implemented. I'm just trying to sort the wood from the trees - don't worry I'd like to see this working too.

[jreading]

Cool, thanks for stepping up!

One thing I wondered though is if a non "import-once" is ever needed. Seems like all imports should be "import-once" so wondering if the extra command is even necessary.

[barryvdh]

So is this implemented or not? Can't find it in the docs..

[ljharb]

I strongly agree - importing once should be the default, since I can't come up with a reason you'd ever want to import multiple.

[mjackson]

+1 There shouldn't be any need for @import-once. It should be the default behavior of @import. @cloudhead, what do you think?

[Soviut]

+1 for importing once being the default behaviour.

[lukeapage]

reopened to track

[jakefolio]

+1 for import-once being the default import behavior

[matthew-dean]

+1

@import-once is not needed nor should be present, since @import should result in a single import.

[liorama]

👍
Single imports rule!

[nitm]

👍

[nitzantomer]

👍

[poadi]

👍

[lukeapage]

ok, you all win!

I've changed this to high priority so its on my list of things to do when I get a chance.

unless anyone wants to make a pull request?

[ljharb]

sorry for the multiple mentions, i edited my commit message a few times. @agatronic will pull request #1010 work?