lilact 0.15.1 → 0.15.2

package/docs/static/demos/error-callback.jsx

@@ -1,29 +1,8 @@
 module.exports = function() {
 
   return <center>
-          <button onClick={()=>{doUnknown()}}>
-            Press to get Error with Curly Brackets!
-          </button>
-          <br/><br/>
           <button onClick={()=>doUnknown()}>
-            Press to get Error without Curly Brackets!
+            Press to get Error!
           </button>
-
-          <p>The first button's onClick arrow handler body is wrapped in curly brackets. <br/><br/>
-
-            {"<button onClick={()=>{doUnknown()}}>"}<br/><br/>
-
-            JS runtimes currently lack a consistent reporting mechanism for errors produced in eval,
-            and as Lilact runs the transpiled JSX in eval, tracing errors has its own difficulties.
-            <br/><br/>
-            At the moment things work pretty nice and errors are tracked to the JSX scripts in
-            {" "}<b>Firefox</b>{" "}and{" "}<b>Chrome</b>{" "}, but{" "}<b>Safari</b>{" "}
-            has problems sometimes, as it drops the eval frame data on async or deferred calls.
-            <br/><br/>
-            Lilact has a tracking mechanism to overcome this, but for the sake of efficiency, 
-            it is block-based and only locates the code that is in  {" {} "} blocks. As a result, the callbacks
-            should be wrapped in a {" {} "} to be tracable in Safari. If not, it works, 
-            but it is not possible to display the exact location of some errors in Safari.</p>
-          </center>
-
+        </center>
 }

package/docs/static/lilact.development.js

@@ -10249,7 +10249,7 @@ function run(jsx, path=`InlineJSX-${++_lilact_jsx__WEBPACK_IMPORTED_MODULE_0__["
 			appendSourcemap: false,
 			blocks_info: _lilact_jsx__WEBPACK_IMPORTED_MODULE_0__["default"].blocks_info,
 
-			injectTraceLabels: true,
+			injectTraceLabels: false,
 		} );
 	}
 	catch(e) {