lazy-loading

问题 I want to have a loaded module configurable. In theory, I want a module that is its own bigger application do receive some configuration. To show / load certain elements depending on the config the main application sends down. I used that with other modules but those where not lazyLoaded. I tried and searched around and have not seen the usage of something like: children: [ { path: 'application-module', loadChildren: () => import('@application-module').then(m => m.ApplicationModule.forRoot({

问题 I've managed to figure out how to lazyload images on my website where the images are called into the HTML via <img> tags. I used this package on GitHub to accomplish this. However I'm having trouble acomplishing the same thing with CSS background: 's. -Some information on the issue: I created an image menu bar last night that changes image size/position based on the browsers screen (Link provided) . All the images in this image menu bar are called in via background: within the CSS (not

问题 I've managed to figure out how to lazyload images on my website where the images are called into the HTML via <img> tags. I used this package on GitHub to accomplish this. However I'm having trouble acomplishing the same thing with CSS background: 's. -Some information on the issue: I created an image menu bar last night that changes image size/position based on the browsers screen (Link provided) . All the images in this image menu bar are called in via background: within the CSS (not

问题 I've managed to figure out how to lazyload images on my website where the images are called into the HTML via <img> tags. I used this package on GitHub to accomplish this. However I'm having trouble acomplishing the same thing with CSS background: 's. -Some information on the issue: I created an image menu bar last night that changes image size/position based on the browsers screen (Link provided) . All the images in this image menu bar are called in via background: within the CSS (not

问题 I would like to lazy-load a specific element of ElementUI in a Vue component. I tried this: import { Tree } from /* webpackChunkName : "element-ui" */ 'element-ui'; Vue.component(Tree.name, Tree); Vue.use(Tree); And this: { components: { 'el-tree': () => import(/* webpackChunkName : "element-ui" */ "element-ui").then(({Tree}) => Tree) } } But in both cases, the element-ui.js chunk file is not created, and the full library is inserted into the main.js file instead. How do I dynamically import

问题 I would like to lazy-load a specific element of ElementUI in a Vue component. I tried this: import { Tree } from /* webpackChunkName : "element-ui" */ 'element-ui'; Vue.component(Tree.name, Tree); Vue.use(Tree); And this: { components: { 'el-tree': () => import(/* webpackChunkName : "element-ui" */ "element-ui").then(({Tree}) => Tree) } } But in both cases, the element-ui.js chunk file is not created, and the full library is inserted into the main.js file instead. How do I dynamically import

问题 I would like to lazy-load a specific element of ElementUI in a Vue component. I tried this: import { Tree } from /* webpackChunkName : "element-ui" */ 'element-ui'; Vue.component(Tree.name, Tree); Vue.use(Tree); And this: { components: { 'el-tree': () => import(/* webpackChunkName : "element-ui" */ "element-ui").then(({Tree}) => Tree) } } But in both cases, the element-ui.js chunk file is not created, and the full library is inserted into the main.js file instead. How do I dynamically import

问题 See the below example, function doSomething1(){/*needs ss*/const ss = SpreadsheetApp.openById(/*SPREADSHEET_ID*/);} function doSomething2(){/*needs ss*/const ss = SpreadsheetApp.openById(/*SPREADSHEET_ID*/);} function doItAll(){ doSomething1(); doSomething2(); } Instead of calling Spreadsheet in both functions, this could be simplified using globals as const ss = SpreadsheetApp.openById(/*SPREADSHEET_ID*/); function doSomething1(){/*do something with ss*/} function doSomething2(){/*do

问题 See the below example, function doSomething1(){/*needs ss*/const ss = SpreadsheetApp.openById(/*SPREADSHEET_ID*/);} function doSomething2(){/*needs ss*/const ss = SpreadsheetApp.openById(/*SPREADSHEET_ID*/);} function doItAll(){ doSomething1(); doSomething2(); } Instead of calling Spreadsheet in both functions, this could be simplified using globals as const ss = SpreadsheetApp.openById(/*SPREADSHEET_ID*/); function doSomething1(){/*do something with ss*/} function doSomething2(){/*do

问题 I have a pretty large app, which by now has a bundle size of around 2mb combined (3 chunks or so). In order to improve loading times, I decided to start using the relatively new React Lazy. Here's an example of a lazy import: const Wizard = React.lazy(() => import('./components/wizards/Wizard')); I understand the general idea, but I still struggle to understand what's the downside, other than having to wait a bit to load a chunk from time to time. According to what I read, I have no reason to