nyngwang
nyngwang
@janvennemann Am I correct to say that each threads created by `thread-loader` will indeed all read and utilize the `options` passed into each loader, e.g. `babel-loader`, that comes after `thread-loader`...
@alexander-akait Is this question even valid? 1. In webpack5, we can customize the `optimization` option in `webpack.config.js`, and some options like `sideEffects`, `usedExports` are there to achieve tree-shaking. 2. Since...
@alexander-akait > [...] I think we can implement plugin for this, it is not loader work So this issue can be closed?
@alexander-akait So is it still possible to implement tree-shaking of unused CSS classes using `css-loader`? Also, is it correct to say that only CSS modules are tree-shakable?
@alexander-akait Is this one added? If so then this can be closed. If not, I can help update the website of webpack later this/next month.
@otaku What does `@inputs` mean in your code?
> IMO, it should be `custom_entries_view` only feature. What does this mean? Say I want to try the new option by this PR, then what should I do to ensure...
> Having to clear the previous qf list and re-populate it just to jump to a breakpoint feels like very poor UX for me Have the same feeling. > [...]...
@mfussenegger Am I correct to say that the current solution for https://github.com/mfussenegger/nvim-dap/discussions/941 is: 1. Open the quickfix list by `:lua require('dap').list_breakpoints()`. 2. Jump to the breakpoint of interest. 3. Execute...
Can confirm, I just encountered this at the current HEAD a6b6d03.