profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/trueadm/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Dominic Gannaway trueadm @facebook London, United Kingdom I'm a software engineer at @facebook working on Workplace. Former React Core team engineer. Author of @infernojs and t7. Enjoys coding + being a Dad

infernojs/inferno 14920

:fire: An extremely fast, React-like JavaScript library for building modern user interfaces

reactwg/react-18 1838

Workgroup for React 18 release.

nightwolfz/inferno-starter 142

Inferno+Mobx starter project

infernojs/babel-plugin-inferno 71

Transforms JSX to InfernoJS vNodes

infernojs/inferno-typescript-example 60

An example of using TypeScript with Inferno

infernojs/inferno-motion 40

A spring that solves your animation problems.

bvaughn/react 15

A declarative, efficient, and flexible JavaScript library for building user interfaces.

joshburgess/inferno-game-kit 14

A fork of react-game-kit using Inferno instead of React. 255kb → 65kb, -40% CPU time, -25% memory

gaearon/prepack 8

Prepack is a partial evaluator for JavaScript. Prepack rewrites a JavaScript bundle, resulting in JavaScript code that executes more efficiently.

startedvinissimus/next-translate

started time in 2 hours

startedwebpack-contrib/awesome-webpack

started time in 3 hours

issue commentinfernojs/inferno

Question: migrating react app to inferno

I'm trying to get VSCode, ESlint, and TypeScript to all play nicely with Inferno. What's required in updating the create-inferno-app? I'd happily jump on that.

romgrk

comment created time in 4 hours

MemberEvent

startedpostalhq/postal

started time in 7 hours

startedmettle/sendportal

started time in 20 hours

startedufrisk/MemProcFS

started time in 21 hours

startedgoogle/jsonnet

started time in a day

startedtailscale/tailscale

started time in a day

release vegetableman/vandal

v2.0.1

released time in a day

release Bobris/BTDB

26.3.1

released time in a day

release vercel/next.js

v10.2.4-canary.16

released time in 2 days

fork zertosh/nom_locate

A special input type for nom to locate tokens

fork in 2 days

push eventbvaughn/react

Brian Vaughn

commit sha 44e5fb376f64fd18fb660afc09df5f4cccbd208d

Made debug hook source info optional

view details

push time in 3 days

MemberEvent

release vercel/next.js

v10.2.4-canary.14

released time in 3 days

push eventbvaughn/react

Sebastian Markbåge

commit sha 5aa0c5671fdddc46092d46420fff84a82df558ac

Fix Issue with Undefined Lazy Imports By Refactoring Lazy Initialization Order (#21642) * Add a DEV warning for common case * Don't set Pending flag before we know it's a promise * Move default exports extraction to render phase This is really where most unwrapping happen. The resolved promise is the module object and then we read things from it. This way it lines up a bit closer with the Promise model too since the promise resolving to React gets passed this same value. If this throws, then it throws during render so it's caught properly and you can break on it and even see it on the right stack. * Check if the default is in the module object instead of if it's undefined Normally we'd just check if something is undefined but in this case it's valid to have an undefined value in the export but if you don't have a property then you're probably importing the wrong kind of object. * We need to check if it's uninitialized for sync resolution Co-authored-by: Dan Abramov <dan.abramov@me.com>

view details

Andrew Clark

commit sha 48a11a3efc1a3107b07d5f866a26f5abd440885f

Update next React version (#21647) This does not mean that a release of 18.0 is imminent, only that the main branch includes breaking changes. Also updates the versioning scheme of the `@next` channel to include the upcoming semver number, as well as the word "alpha" to indicate the stability of the release. - Before: 0.0.0-e0d9b28999 - After: 18.0.0-alpha-e0d9b28999

view details

Andrew Clark

commit sha bc7d5ac99dcb36679c90b60731458063fb8c82f3

Allow alpha tags

view details

Andrew Clark

commit sha 6bbe7c3446c6ab986be39a678a75f6e2c27a5b52

Remove space from tag arguments

view details

Andrew Clark

commit sha e6be2d531d82be6a601abbd392e4615f90e1f87a

Fix tag validation

view details

Samuel Susla

commit sha 1a3f1afbd3cf815d4e55628cd7d84ef20171bab8

[React Native] Fabric get current event priority (#21553) * Call into Fabric to get current event priority Fix flow errors * Prettier * Better handle null and undefined cases * Remove optional chaining and use ?? operator * prettier-all * Use conditional ternary operator * prettier

view details

Andrew Clark

commit sha aecb3b6d114e8fafddf6982133737198e8ea7cb3

Deprecate ReactDOM.render and ReactDOM.hydrate (#21652) * Use existing test warning filter for server tests We have a warning filter for our internal tests to ignore warnings that are too noisy or that we haven't removed from our test suite yet: shouldIgnoreConsoleError. Many of our server rendering tests don't use this filter, though, because it has its own special of asserting warnings. So I added the warning filter to the server tests, too. * Deprecate ReactDOM.render and ReactDOM.hydrate These are no longer supported in React 18. They are replaced by the `createRoot` API. The warning includes a link to documentation of the new API. Currently it redirects to the corresponding working group post. Here's the PR to set up the redirect: https://github.com/reactjs/reactjs.org/pull/3730 Many of our tests still use ReactDOM.render. We will need to gradually migrate them over to createRoot. In the meantime, I added the warnings to our internal warning filter.

view details

Samuel Susla

commit sha c96b78e0e7cd9e6ef7c0464748a50cf8510dde81

Add concurrentRoot property to ReactNativeTypes (#21648) * Add concurrentRoot property to ReactNativeTypes * Add concurrentRoot to ReactNativeType * Use ReactFabricType instead of ReactNativeType

view details

Sebastian Markbåge

commit sha c1536795cae5101041ef50a59ae29119aa1c2bf4

Revert "Make enableSuspenseLayoutEffectSemantics static for www (#21617)" (#21656) This reverts commit 39f00748922cf40e06cd08d0c81f8b28fc8503fa.

view details

Timothy Yung

commit sha cb30388d10240363615fef31eb16b9d4e2925bb9

Export React Native `AttributeType` Types (#21661)

view details

Brian Vaughn

commit sha 01be61c12f4361dc9e4c4f4157bffbeb0e57b064

DevTools can inspect Proxies that return broken iterator functions (#21660)

view details

Brian Vaughn

commit sha 8bfb22f9447d06540b2e44a104b52a58ff5e93d7

Small tweaks

view details

Brian Vaughn

commit sha 79de6a79f77cb26a11efeb35aba09f7ad6aeee27

Merge branch 'master' into devtools-named-hooks

view details

push time in 3 days

delete branch bvaughn/react

delete branch : issues/21654

delete time in 3 days

push eventbvaughn/react

Brian Vaughn

commit sha c24f78ad440cd2c8bb543e07c490e65cb9933db1

DevTools can inspect Proxies that return broken iterator functions

view details

push time in 3 days

create barnchbvaughn/react

branch : issues/21654

created branch time in 3 days

release vercel/next.js

v10.2.4-canary.13

released time in 3 days

push eventbvaughn/react

Brian Vaughn

commit sha 9833d00bfa764ccbb2447e66a94afe2fb57b2cf4

Updated hook names cache to account for new Suspense APIs This commit is not fully working but it does load and parse hooks from a test Code Sandbox app so I'm going to check it in as a work-in-progress.

view details

push time in 4 days

startedmarko-js/marko

started time in 4 days

release microsoft/vscode

1.57.0

released time in 4 days

fork paulirish/ecma402-fix-lookup-matcher

Ecma-402 proposal for fixing its LookupMatcher algorithm (9.2.2 and 9.2.3)

fork in 4 days

startedcalendso/calendso

started time in 4 days

startedisaachinman/next-i18next

started time in 4 days

startedcamspiers/snap

started time in 4 days

startedtauri-apps/wry

started time in 4 days