Brian M Hunt

@ManrajGrover tko.utils (where this was merged) passes: https://circleci.com/gh/knockout/tko-policy There are a long list of build & testing issues with knockout. See e.g. #1360 .

Yes, we will have an eslint test on checking for the tko family of packages too at some point. :)

I agree this should be supported. Needs a few tests and some work-through. Cheers @mfeineis

It's a good point, thanks for the thought @Elephant-Vessel . One thing of note, you might be interested in doing the mucking around at the data layer with a computed-casting...

Conceptually I think this is useful, but we'd need to make sure it's consistent with the fast-foreach API in tko (since folks may move back-and-forth); the tko API is more...

Aside: that it may be worth capping the number of worker threads based on the hardware e.g. ```ts const maxProcs = Math.max(navigator.hardwareConcurrency - 1, 1) ``` Note that [`navigator.hardwareConcurrency`](https://developer.mozilla.org/en-US/docs/Web/API/NavigatorConcurrentHardware/hardwareConcurrency) is...

Thanks, that's great to know. In the case of many similarly small files, what about a "fire and forget" thread system. Does eliminating the requirement of figuring out when a...

Thanks for the update @mrjoelkemp . I think that's pretty much it. I didn't see any exposed code in Webpack to allow use of require.context externally, and I did a...

Not sure, but perhaps food for thought since Wallaby supports multiple entries: https://github.com/jeffling/wallaby-webpack Cheers!

@jbaicoianu Thanks for sharing that; this information will undoubted help others who happen across this.