Simen Bekkhus comments

Results 1245 comments of


                                            Simen Bekkhus

`vm.compileFunction(source)` is much slower than `new vm.Script(source)`

@bnoordhuis reading your comment more closely, I see you're talking about `contextExtensions`. We don't use that, we use `parsingContext` - does that have the same limitations you think?

`vm.compileFunction(source)` is much slower than `new vm.Script(source)`

Just as a follow up here, these are the numbers I'm seeing with the latest 20.8 (nothing new, just posting to say it's still an issue). ```sh-session $ nvm run...

`vm.compileFunction(source)` is much slower than `new vm.Script(source)`

Ooh, any workaround, even with caveats, would be awesome! 😃 > The performance hit would comeback again if you intent to support `import()` We do support that, but I believe...

`vm.compileFunction(source)` is much slower than `new vm.Script(source)`

Amazing! ♥️

`vm.compileFunction(source)` is much slower than `new vm.Script(source)`

Can confirm the PR above works - gives these results on my machine with the repo from the OP ``` Running with Script took 20 ms Running with compileFunction took...

`vm.compileFunction(source)` is much slower than `new vm.Script(source)`

Ooh, exciting! Using `compileFunction` simplifies the implementation in Jest quite a bit!

TypeScript 5.5 compatibility for `ObservableSet`

Duplicate of #3850

docs: update nodejs versions to 22 in README.md

> I'm also thinking about updating docker compose example too. Is it OK to do it in this PR? > > ```yaml > services: > node: > image: "node:22" >...

Jest with TypeScript and ES modules can't import "named imports" from cjs modules

Can anyone provide an example of where node is able to import using native ESM, but Jest fails? E.g. React does not support native ESM: https://github.com/facebook/react/issues/11503

[Bug]: isEqual with large Float64Arrays is slow

Thanks for the great reproduction 👍 I've got a fix for this in https://github.com/jestjs/jest/pull/15178, but only when using `toStrictEqual` (although it also makes `toEqual` use 100m instead of 500ms). As...