tdumitrescu / virtual-jade Goto Github PK

when released

• use the jade parser module separately

• don't bother rendering empty {}s or []s
• don't bother wrapping expressions in [] if there is only 1 element
• classes
  • don't bother .filter(Boolean) class arrays with only literals
  • concatenate compile-time them whenever possible

Jade/Pug allows each val, key in {...}: https://pugjs.org/language/iteration.html

one that handles arrays better

Currently when compiling with webpack, debugging an issue inside virtual-jade compilation is very hard.

The output is quite verbose. Source map support that maps to jade would be a time saver.

• browserify
• webpack
• duo
• component

Error: the "filename" option is required to use "extends" with "relative" paths
at Parser.resolvePath (D:\demows\koa-demo\node_modules\jade\lib\parser.js:486:13)
at Parser.parseExtends (D:\demows\koa-demo\node_modules\jade\lib\parser.js:505:21)
at Parser.parseExpr (D:\demows\koa-demo\node_modules\jade\lib\parser.js:221:21)
at Parser.parse (D:\demows\koa-demo\node_modules\jade\lib\parser.js:122:25)
at render (D:\demows\koa-demo\node_modules\virtual-jade\lib\index.js:43:25)
at DestroyableTransform.CompileJade as _transform
at DestroyableTransform.Transform._read (D:\demows\koa-demo\node_modules\through2\node_modules\readable-stream\lib_stream_transform.js:159:10)
at DestroyableTransform.Transform._write (D:\demows\koa-demo\node_modules\through2\node_modules\readable-stream\lib_stream_transform.js:147:83)
at doWrite (D:\demows\koa-demo\node_modules\through2\node_modules\readable-stream\lib_stream_writable.js:313:64)
at writeOrBuffer (D:\demows\koa-demo\node_modules\through2\node_modules\readable-stream\lib_stream_writable.js:302:5)

• class -> className
• data-* -> dataset.*

• case
• classes
• caching
• mixins
• dependencies
• interpolation
• content
• while loops
• each
• escape and unescaped