Webpack loader announce #3

Activity

1. atomictag

   added

   enhancement

   on Jun 9, 2017
2. atomictag commented on Jun 9, 2017

   

   atomictag

   on Jun 9, 2017

   Owner

   More actions

   Awesome! Many thanks! Let me know if you find the library useful
3. blikblum commented on Jun 9, 2017

   

   blikblum

   on Jun 9, 2017

   Author

   More actions

   I think it will help a lot of people to migrate for more performant rendering strategy
4. atomictag commented on Jun 9, 2017

   

   atomictag

   on Jun 9, 2017

   Last edited by atomictag

   Owner

   More actions

   cool. BTW, in case you try to get a reference to the current element from a helper - e.g. to do something a la innerHtml or to decorate the element being patched, IncrementalDom.currentElement()and IncrementalDom.currentPointer()are not going to help - because your helper is going to be called before the element is actually created. In order to do that you'll need to provide a (relatively trivial) extension to IncrementalDom in order to "pass back" the node returned by elementOpen, elementOpenEnd, elementVoid and text
5. blikblum commented on Jun 10, 2017

   

   blikblum

   on Jun 10, 2017

   Author

   More actions

   IncrementalDom.currentElement()and IncrementalDom.currentPointer() are not going to help - because your helper is going to be called before the element is actually created

   I managed to access the current element by putting the interpolation {{setInnerHTML short_bio}} after the element. But the issue is that calling skip gives an error because the the helper is called inside a IncrementalDOM.text call.

   In order to do that you'll need to provide a (relatively trivial) extension to IncrementalDom in order to "pass back" the node returned by elementOpen, elementOpenEnd, elementVoid and text

   I can not see how it could be done

   AFAIK the only way to do that would be creating a way to put raw script in the code, something that superviews does with the <script> tag
6. coldwhitelight commented on Nov 7, 2017

   

   coldwhitelight

   on Nov 7, 2017

   More actions

   Hello,

   I've got a specific case, where 90% of the app templates will be precompiled but some may be compiled on page load or loaded from an external source (ajax) and compiled on the spot.

   I already use incremental-bars with incremental-bars-loader for Webpack and it seems to work with this example:

   // this is in my index.js
   
   import IncrementalDOM from 'incremental-dom';
   import Handlebars from 'handlebars/runtime';
   
   // this is compiled by incremental-bars-loader.
   var template = require("../templates/baselayout.tpl");
   
   // This works.
   IncrementalDOM.patch(el, template, {title: 'Test'});
   

   However I cannot load incremental-bars to be used in browser in any way.
   I know it's not supposed to be done that way, but is there any way I can still include it with Webpack? Or at least build myself a dist version of the script to include as an external?

   Including it like that:

   var Handlebars = require('incremental-bars');
   

   gives me a lot of warnings and some errors:

   > TypeError: Cannot read property '_' of undefined
   (...)
   
   > ./node_modules/handlebars/lib/index.js
   require.extensions is not supported by webpack. Use a loader instead.
   (...)
   
   > client:147 ./node_modules/html-minifier/node_modules/uglify-js/tools/node.js
   7:11-32 Critical dependency: the request of a dependency is an expression
   (...)
   

   Any help would be really appreciated, thank you.
7. atomictag commented on Nov 7, 2017

   

   atomictag

   on Nov 7, 2017

   Last edited by atomictag

   Owner

   More actions

   I personally don't use webpack so perhaps someone with more experience with that can chime in. I guess it's not a difficult task to make it work - given the very limited amount of dependencies.

   OTOH, it may makes sense to use the standard Handlebars compiler for those 10% pages that requires on-the-fly compilation.
8. coldwhitelight commented on Nov 7, 2017

   

   coldwhitelight

   on Nov 7, 2017

   Last edited by coldwhitelight

   More actions

   Thanks,

   It probably isn't difficult, but I'm starting out in this department.
   I can't use standard Handlebars, as I want to forward the compiled template to IncrementalDOM.patch(), so I need it compiled by incremental-bars, not handlebars.

   Unless there's a way I don't know about?

   Edit: So there's no easy way to get a working incremental-bars.js file to include I suppose?
9. atomictag commented on Nov 7, 2017

   

   atomictag

   on Nov 7, 2017

   Owner

   More actions

   well, you could use IncrementalDOM.patch(el,...) for idom-compiled templates and el.innerHtml = ... (or similar) for your html-string-compiled templates. That's by far simpler and more performant than any other option I can think of
10. coldwhitelight commented on Nov 7, 2017

    

    coldwhitelight

    on Nov 7, 2017

    Last edited by coldwhitelight

    More actions

    Allright, thanks for help, I'll try that!
    Hopefully someone has an idea on how to make it work.