Open stillnaughty opened 5 years ago
gabek
commented
5 years ago Having custom pipes would be fantastic. Personally I have a use case where I wish I could render to a custom format, and piping the markdown to my external tool would resolve that. Sure, it might be slow, but it would be extensible.
Jos512
commented
5 years ago JS Uglification. - It's further minimize the size & protect the front-end JS code which is quite essential at least to our operation.
For minification Hugo uses minify, which is a great tool but hasn't developed its JavaScript minification capabilities as well. There's a long standing issue to do that here.
stale[bot]
commented
5 years ago This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.
Awesome in Hugo pipes @v0.53~! Great work thumbup~!!
Meanwhile in using Hugo pipes there's still a few features that truly wish Hugo pipes resources function can add into it. Or can we include our "custom" functions/plugins and called by resources functions btw?
• JS Uglification. - It's further minimize the size & protect the front-end JS code which is quite essential at least to our operation. • linting - for managing code standard across the team linting is quite useful on both SASS & JS (Indeed SASS linting can be included in postCSS, but sadly resources.postCSS is called after resources.ToCSS, Or there's any workaround on this?) • ES6 (Babel) support - there's not much to say on this as I've seens suggestions from others before.
Truly wish such features will be included soon~~!