While testing this package out as an NPM install, one way to efficiently hoist the framework into a project was to hoist tachyons.scss out of node_modules and into the project itself. We could then adjust paths to modules to include the module name eg:
@use "tachyons-haru-sass/scss/modules/any-module"
The problem here is that it is not possible to change the variables, without messing with files inside the package.
- A part of the solution is to
@forward the variables in tachyons.scss (which we are already doing), but we also need to @use them from the tachyons namespace rather than pointing directly to the @use "/sass/variables .scss" as we currently do.
This should mean that we can then re-declare the variables file to one in a new location, and the project will render as long as the namespace matches.
While testing this package out as an NPM install, one way to efficiently hoist the framework into a project was to hoist
tachyons.scssout ofnode_modulesand into the project itself. We could then adjust paths to modules to include the module name eg:The problem here is that it is not possible to change the variables, without messing with files inside the package.
@forwardthe variables in tachyons.scss (which we are already doing), but we also need to@usethem from thetachyonsnamespace rather than pointing directly to the@use "/sass/variables .scss"as we currently do.This should mean that we can then re-declare the variables file to one in a new location, and the project will render as long as the namespace matches.