Tobias Koppers

> This has already been fixed in the master branch, but the published code on npm doesn't match the tag in the repo (very bad 😢 ). I meant on...

@jvmccarthy Do you want to maintain this loader? I'm unable to decide this from code and don't have the time to test it.

``` js const useCallback = (fn, args) => { const callback = useMemo(() => { if (__DEV__) { if (fn.length !== args.length) warning(...); } const callback = () => fn(...callback.args);...

@sophiebits That's clever and would have none of the problems with args, etc. It even doesn't require a dependencies list. One nitpick: `return useCallback((...args) => (0, ref.current)(...args), []);` to pass...

> @sokra With this you will not be able to access to state and props updates inside a callback. I think with @sophiebits' approach this will work. The latest function...

> ```ts > Should type & category turn into getter instead of readonly? > ``` yes, that seem to work

Seem to be another problem. Here runtimeChunk and splitChunks for the initial chunks is used...

You can disable real content hashing with `output.realContentHash: false` to get the webpack 4 behavior.

Seems like a useful change. As first step we can add support for `file://` urls when processing the source map. This seems like a non-breaking change to me. Do you...

The equal external to a false alias would be: `externals: { "node:fs": "{}" }`