You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately the visitor approach doesn't work without monkey patching the LESS ImportVisitor that runs while the tree is still being constructed. Plugin visitors unfortunately aren't run until the tree is complete. Considering that I'll be implementing this as a file manager.
Resolved to use new 'locate://' & 'pkg://' path schemes to denote module identifiers to rewrite. These changes will also replace the existing LOCATE & ~ behaviour in steal itself.
stealjs/steal#565 adds a
LOCATE()
macro where files like less and css can use it to change a url to a path located bySystem.locate
. For example:might get converted to:
The code for that extension starts here: https://github.com/stealjs/steal/pull/565/files#diff-abc90bebf14055b4190455e9af84a13eR1.
The problem with LESS, LOCATE, and @imports is that the
@import
ed fill will be processed with LESS which doesn't allow the LOCATE hook to run.The solution to this is to write a less plugin. I explained this better here: less/less.js#2792
The solution is to make a less plugin that gets added when we "render" some less into CSS here: https://github.com/stealjs/steal-less/blob/master/less.js#L43
Plugins are documented here: http://lesscss.org/usage/#plugins
Notice that plugins can be added during render like:
There are two options how the plugin could work.
Completely take over path resolution.
My guess is that the plugin will look like the npm-file-manager here: https://github.com/less/less-plugin-npm-import/blob/master/lib/npm-file-manager.js#L6
In this case
LOCATE
wouldn't be needed.Look for LOCATE ourselves
In this case, it's likely we can use the "visitor" approach and identify when
LOCATE
is found and rewrite the AST less uses. I think this plugin does this: https://github.com/less/less-plugin-inline-urls/tree/master/libTake over loadFile
Similar to the npm-file-manager, we might be able to pre-process the source before it gets to less. Possibly by overwriting
loadFile
orloadFileSync
.This might be the easiest way of getting it done.
The text was updated successfully, but these errors were encountered: