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
By default, if any of your PostCSS plugins raise a warning it will be displayed using console.error. You can override this behavior by passing a function as the second argument to PostStylus.
Running"stylus:lint"(stylus)taskVerifyingpropertystylus.lintexistsinconfig…OK
Files: KiraGoddess.styl->KiraGoddess.css
Options: banner="",compress,use=[null]ReadingKiraGoddess.styl…OKWarning{type: 'warning',text:
'CSS3 tab-size not supported by: IE (11), Edge (18), IE Mobile (11) and only partially supported by: Safari (12), iOS Safari (12.0-12.1), Opera Mini (all), Blackberry Browser (10) (css3-tabsize)',line: 1,column: 12,node:
Declaration{raws: {before: '',between: ':'},type: 'decl',parent:
Rule{raws: [Object],type: 'rule',nodes: [Array],parent: [Root],source: [Object],selector: '.KiraClass',lastEach: 2,indexes: {}},source: {start: [Object],input: [Input],end: [Object]},prop: 'tab-size',value: '4'},plugin: 'doiuse'}0[Warning{type: 'warning',text:
'CSS3 tab-size not supported by: IE (11), Edge (18), IE Mobile (11) and only partially supported by: Safari (12), iOS Safari (12.0-12.1), Opera Mini (all), Blackberry Browser (10) (css3-tabsize)',line: 1,column: 12,node:
Declaration{raws: [Object],type: 'decl',parent: [Rule],source: [Object],prop: 'tab-size',value: '4'},plugin: 'doiuse'}]WritingKiraGoddess.css…OKFileKiraGoddess.csscreated.>>1filecreated.Done.Thecommand"grunt stylus --verbose"exitedwith0.
6. Not helped
6.1. failOnError: true
I didn't find in PostStylus documentation setting, similar as failOnError: true of Grunt PostCSS. For example, this configuration doesn't solve the problem.
1. Summary
Docs says:
But if PostCSS doiuse plugin show warnings, build no failed.
2. Environment
Operating system:
package.json
:3. MCVE
3.1. Live demo
3.2. Data
Gruntfile.coffee
:KiraGoddess.styl
:KiraGoddess.css
:3.3. Steps to reproduce
4. Expected behavior
For PostCSS equivalent command build failed:
5. Actual behavior
For PostStylus command build passed:
6. Not helped
6.1. failOnError: true
I didn't find in PostStylus documentation setting, similar as
failOnError: true
of Grunt PostCSS. For example, this configuration doesn't solve the problem.6.2. Warning Handler
console.error
in examples as below also doesn't solve the problem.Thanks.
The text was updated successfully, but these errors were encountered: