Changes between Initial Version and Version 1 of Ticket #6310, comment 21


Ignore:
Timestamp:
03/27/2018 09:44:23 AM (21 months ago)
Author:
agiammarchi
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6310, comment 21

    initial v1  
    44  3. we have different pages to target, and we use SASS to deal with CSS imports too (we used SASS to deal with variables too but since we've dropped Edge 15 we can use native CSS variables already). We need to bundle pages, not just JS, with optional assets. AFAIK every new file would require changes in the manifest too (thinking of source map here), which is also one of the reasons we went for the current strategy: no need to change anything in the manifest. As summary, if we'll ever end up creating just desktop-options.html/js/css, I'd say we wait for our component refactory to happen and only after we see what we've learned and what's the best solution to go. Unless, of course, Webpack can solve everything through its opinionated nature (if that's even the case, I know Webpack is actually very configurable but not so easy to configure). 
    55 
    6 Thanks in advance for any sort of follow up. I know release made everyone very busy but since I am doing some refactory to be able to improve the UI the sooner I know how to bundle my components the better. 
     6Thanks in advance for any sort of follow up. I know release made everyone very busy, but since I am doing some refactory to be able to improve the UI, the sooner I know how to bundle my components, the better. 
    77 
    88Regards.