very rough approach to an @import feature #12

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
2 participants
@mikesmullin

i obviously need help finishing it, but i don't think it would be much more than this?

@balupton

This comment has been minimized.

Show comment Hide comment
@balupton

balupton Aug 26, 2011

Owner

I like your commitment and good start :) things to take into consideration:

@import in comments or strings, you'll probably want to only check a header comment defined at the start of the document

What happens with circular references?

What happens when a file is referenced multiple times? Is the correct order always determined? Naturally the file will now have multiple positions, so there needs to be some algorithm to compensate for this?

what are your thoughts? Definitely looking forward to how this progressed :) keep up the great work

Owner

balupton commented Aug 26, 2011

I like your commitment and good start :) things to take into consideration:

@import in comments or strings, you'll probably want to only check a header comment defined at the start of the document

What happens with circular references?

What happens when a file is referenced multiple times? Is the correct order always determined? Naturally the file will now have multiple positions, so there needs to be some algorithm to compensate for this?

what are your thoughts? Definitely looking forward to how this progressed :) keep up the great work

@mikesmullin

This comment has been minimized.

Show comment Hide comment
@mikesmullin

mikesmullin Dec 16, 2012

using mincer now. probably will use this for only minification, but more likely will just use gaze or grunt + google closure binary + gzip.

using mincer now. probably will use this for only minification, but more likely will just use gaze or grunt + google closure binary + gzip.

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