Open Mase3206 opened 2 months ago
Thanks for providing a public repo, helps a whole bunch!!!
It seems your configurations are correct and things should work... checking some of the Action logs it looks like at points it may have been attempting to write to non-existent sub-directories, and at some point it also looks like ya forked and fixed things too :-D
Tip for faster debugging; it be possible to test this Action locally, all the options can be defined via shout-casing the keys and prefixing with INPUT_
, for example setting the input/output paths within the package.json
- "test": "node index.js"
+ "test": "INPUT_SOURCE=test/simple.scss INPUT_DESTINATION=/tmp/simple.css node index.js",
... Let me know if ya want to merge in those fixes and I'll happily accept you as a contributor to this project!
That tip for local testing is super helpful, thank you!
I'm still working on my fork. Things went waaaay deeper than expected, and I'm still unable to get the Sass JS API to cooperate. I'm a full time student and my classes just got super busy for a moment, so it will probably be a bit before I can keep digging into it.
Describe the bug
I haven't been able to get this action to:
I have tried:
sourceMap
to the desired map file path - seemingly no map is generatedsourceMap
to true andoutFile
to the desired map file output - no output, but it did attempt to update the link in the compiled CSSomitSourceMapUrl
to false - didn't seem to do anythingsourceMap
andsourceMapEmbed
to true - it did not embed the mapI even manually checked both the post-compile artifacts and the post-Pages publish artifacts for a map file or embedded map, but none of them had either.
To Reproduce
Feel free to browse through my commit history for my workflow file: deploy-to-pages.yml
Expected behavior
I would have expected a map file to be generated.