-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there a source maps support? #25
Comments
With new csso itself having them now this should be possible. Will look into it |
in the CSSO have this opportunity but csso-rails setup this is not possible to include the generation of files, there is only the option of code restructuring. |
Released 0.5.0 with support for sourcemaps, please test |
Я обновился до 0.5.0 внес изменения в свой файл config.rb (compass)
если использовать работу без source maps все работает как и работало, если сделать поддержку генерации maps то выдает ошибку
|
@maxicms Also it does not combine source maps in standalone, only via sprockets 4 (yep, have to run compress phase twice in current version) So code will look like #...
compressed_css,compressed_map = Csso.optimize_with_sourcemap(css, file)
combined_map = ... # here combine map from File.read(map) and compressed_map
result = AutoprefixerRails.process(compressed_css,
from: file,
to: file,
map: { prev: combined_map, inline: false })
File.open(file, 'w') { |io| io << result.css }
File.open(map, 'w') { |io| io << result.map } |
with return parameters understood thanks, but even if you disable AutoprefixerRails then the output is optimized file in which there is no line / * # sourceMappingURL = bootstrap.css.map * / |
Csso handles css as strings, it has no way of knowing what the url is going to be, you have to add that line yourself |
very strange, as triggered by csso gulp or grunt work normally and processed at the end of a link to the css file. And in the css source code that compiles it also has a compass. |
whether it is possible to include support for the creation of source maps?
The text was updated successfully, but these errors were encountered: