A Google Chrome extension to display Javascript frameworks used on a website.
kassens/fire 11
MooTools Fire - Sets AIR on Fire
kassens/javascript-formatter 8
A Javascript formatter written in Javascript using a PEG
Complex Event Processing implementation for EScala
vector drawing for buttons, icons, widgets and all that stuff
Simple desktop widgets based on MacRuby. Highly experimental.
Directory bookmarks for the shell
CouchApp TextMate bundle
A RESTful CouchDB client based on Heroku's RestClient and Couch.js - you want the version at http://github.com/couchrest/couchrest/tree/master
startedMayaPosch/NymphCast
started time in a day
startedrxhanson/Rectangle
started time in 2 days
PR opened facebook/relay
Not sure what the intended styles were here. But the "button" class makes the text white, making it completely invisible.
Removing the class makes the link show up in orange color with an underline on hover:
pr created time in 2 days
PR opened facebook/relay
The previous link doesn't work.
pr created time in 2 days
create barnchrelayjs/eslint-plugin-relay
branch : dependabot/npm_and_yarn/glob-parent-5.1.2
created branch time in 2 days
PR opened relayjs/eslint-plugin-relay
Bumps glob-parent from 5.1.1 to 5.1.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/gulpjs/glob-parent/releases">glob-parent's releases</a>.</em></p> <blockquote> <h2>v5.1.2</h2> <h3>Bug Fixes</h3> <ul> <li>eliminate ReDoS (<a href="https://github-redirect.dependabot.com/gulpjs/glob-parent/issues/36">#36</a>) (<a href="https://github.com/gulpjs/glob-parent/commit/f9231168b0041fea3f8f954b3cceb56269fc6366">f923116</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/gulpjs/glob-parent/blob/main/CHANGELOG.md">glob-parent's changelog</a>.</em></p> <blockquote> <h3><a href="https://github.com/gulpjs/glob-parent/compare/v5.1.1...v5.1.2">5.1.2</a> (2021-03-06)</h3> <h3>Bug Fixes</h3> <ul> <li>eliminate ReDoS (<a href="https://github-redirect.dependabot.com/gulpjs/glob-parent/issues/36">#36</a>) (<a href="https://github.com/gulpjs/glob-parent/commit/f9231168b0041fea3f8f954b3cceb56269fc6366">f923116</a>)</li> </ul> <h2><a href="https://www.github.com/gulpjs/glob-parent/compare/v5.1.2...v6.0.0">6.0.0</a> (2021-05-03)</h2> <h3>⚠ BREAKING CHANGES</h3> <ul> <li>Correct mishandled escaped path separators (<a href="https://github-redirect.dependabot.com/gulpjs/glob-parent/issues/34">#34</a>)</li> <li>upgrade scaffold, dropping node <10 support</li> </ul> <h3>Bug Fixes</h3> <ul> <li>Correct mishandled escaped path separators (<a href="https://github-redirect.dependabot.com/gulpjs/glob-parent/issues/34">#34</a>) (<a href="https://www.github.com/gulpjs/glob-parent/commit/32f6d52663b7addac38d0dff570d8127edf03f47">32f6d52</a>), closes <a href="https://github-redirect.dependabot.com/gulpjs/glob-parent/issues/32">#32</a></li> </ul> <h3>Miscellaneous Chores</h3> <ul> <li>upgrade scaffold, dropping node <10 support (<a href="https://www.github.com/gulpjs/glob-parent/commit/e83d0c5a411947cf69eb58f36349db80439c606f">e83d0c5</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/gulpjs/glob-parent/commit/eb2c439de448c779b450472e591a2bc9e37e9668"><code>eb2c439</code></a> chore: update changelog</li> <li><a href="https://github.com/gulpjs/glob-parent/commit/12bcb6c45c942e2d05fc1e6ff5402e72555b54b6"><code>12bcb6c</code></a> chore: release 5.1.2</li> <li><a href="https://github.com/gulpjs/glob-parent/commit/f9231168b0041fea3f8f954b3cceb56269fc6366"><code>f923116</code></a> fix: eliminate ReDoS (<a href="https://github-redirect.dependabot.com/gulpjs/glob-parent/issues/36">#36</a>)</li> <li><a href="https://github.com/gulpjs/glob-parent/commit/0b014a7962789b2d8f2cf0b6311f40667aecd62c"><code>0b014a7</code></a> chore: add JSDoc returns information (<a href="https://github-redirect.dependabot.com/gulpjs/glob-parent/issues/33">#33</a>)</li> <li><a href="https://github.com/gulpjs/glob-parent/commit/2b24ebd64b2a045aa167c825376335555da139fd"><code>2b24ebd</code></a> chore: generate initial changelog</li> <li>See full diff in <a href="https://github.com/gulpjs/glob-parent/compare/v5.1.1...v5.1.2">compare view</a></li> </ul> </details> <br />
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
<details> <summary>Dependabot commands and options</summary> <br />
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
</details>
pr created time in 2 days
push eventfacebook/relay
commit sha ba25a04668bde1a205e33d24a2478483c7330989
Deploying to gh-pages from @ f1f07ff390a30e581e6b260fb39931282eba8b77 🚀
push time in 2 days
push eventfacebook/relay
commit sha f1f07ff390a30e581e6b260fb39931282eba8b77
Bump crossbeam from 0.7 to 0.8, lsp from 0.3 to 0.5, lsp-types from 0.73 to 0.89 Reviewed By: alunyov, dtolnay Differential Revision: D29056473 fbshipit-source-id: 9434e9e0895d82482f4c70afa01a2f77702b965f
push time in 2 days
push eventfacebook/relay
commit sha 2ac9c7ea3a85a80548347d2c4dbbfa7e9338a3eb
Deploying to gh-pages from @ 8fe69804d2c04686ecb56ffcce8e5d9df1907ef8 🚀
push time in 2 days
push eventfacebook/relay
commit sha 8fe69804d2c04686ecb56ffcce8e5d9df1907ef8
Don't generate raw response type for @no_inline fragments when not needed Reviewed By: kassens Differential Revision: D29074508 fbshipit-source-id: 266da7d94204c462b6ba90138c24f678117ed856
push time in 2 days
push eventfacebook/relay
commit sha cc42c0b32038ed6d75f727ff5bb9802ea73364af
Deploying to gh-pages from @ 9fef6cc3831d10526fee820ad15b5f63a4e096b5 🚀
push time in 2 days
push eventfacebook/relay
commit sha 9fef6cc3831d10526fee820ad15b5f63a4e096b5
pre-suppress this typing errors ahead of 154 Reviewed By: samwgoldman Differential Revision: D29065246 fbshipit-source-id: f418041305a46df410dcbe3d9a4db81a61ac7014
push time in 2 days
push eventfacebook/relay
commit sha f80a0e7df20068a37e3aab2c3bbc01172f7ea81a
Deploying to gh-pages from @ 99937ec7fa681754c7a3d45f49b330b1753bf0d2 🚀
push time in 3 days
push eventfacebook/relay
commit sha 99937ec7fa681754c7a3d45f49b330b1753bf0d2
Fix flag initialization in test RelayModernEnvironment-ExecuteWithSiblingAndNestedModule-test.js Reviewed By: tyao1 Differential Revision: D29045240 fbshipit-source-id: 7c24d3f054795861683555fc580bb918cfc35a68
push time in 3 days
startedkassens/relay-cra-example
started time in 3 days
push eventfacebook/relay
commit sha fe7e82d7f40054603ebb8cb936e17c592cc84a98
Deploying to gh-pages from @ b9957fdce680ee70845e587885cf33d1bee480d6 🚀
push time in 3 days
push eventfacebook/relay
commit sha b9957fdce680ee70845e587885cf33d1bee480d6
Remove jest.resetModules(...) in RelayReferenceMarker-test.js Reviewed By: kassens Differential Revision: D29067216 fbshipit-source-id: df71b196c27807640ff009c33b303b580f3a879e
push time in 3 days
push eventfacebook/relay
commit sha 9957960f487f5ce28c98fc07b6d73f1789576d5a
Deploying to gh-pages from @ 9d86b349a1aa9c17540aa21ae131b416c90ed81d 🚀
push time in 3 days
pull request commentfacebook/relay
Fix: Check if global exists before calling ErrorUtils
@poteto merged this pull request in facebook/relay@9d86b349a1aa9c17540aa21ae131b416c90ed81d.
comment created time in 3 days
push eventfacebook/relay
commit sha 9d86b349a1aa9c17540aa21ae131b416c90ed81d
Fix: Check if global exists before calling ErrorUtils (#3465) Summary: I was experiencing some `global is not defined`'s from `RelayPublishQueue.js` when using Relay in Vite. And I think this change will solve it for the cases where global is not yet defined. Pull Request resolved: https://github.com/facebook/relay/pull/3465 Reviewed By: tyao1 Differential Revision: D28937317 Pulled By: poteto fbshipit-source-id: d95b9f3cda1fa6325a992e2886d2886c8833a134
push time in 3 days
PR closed facebook/relay
I was experiencing some global is not defined's from RelayPublishQueue.js when using Relay in Vite. And I think this change will solve it for the cases where global is not yet defined.
pr closed time in 3 days
push eventfacebook/relay
commit sha 2c45d45675b9e5da393899cf704bcb84a290ddca
Deploying to gh-pages from @ b9f8d6246096dc984198993a2f163f709445d4f7 🚀
push time in 3 days
push eventfacebook/relay
commit sha b9f8d6246096dc984198993a2f163f709445d4f7
Parallelize more of the persist_operations Reviewed By: alunyov Differential Revision: D29053309 fbshipit-source-id: 9c148c845684954a25d82f110f26217b090da21d
push time in 3 days
push eventyungsters/react
commit sha 83bdc565f9921c341d558e29401d20151166695b
Remove @octokit/rest dependency from DevTools (#21317)
commit sha 7becb2ff1befe8788f30268ebd8ad59aefcdb4f1
DevTools version bump 4.12.3 -> 4.12.4
commit sha cdb6b4c554bb40654d6c3e72f06b29003bec8dc7
Only hide outermost host nodes when Offscreen is hidden (#21250)
commit sha a3a7adb83ea28667714df91ef7e03dbe358330c3
Turn off enableSyncDefaultUpdates in test renderer (#21319)
commit sha 78120032d4ca7ee8611d630d7c67e7808885dfe9
Remove `flushDiscreteUpdates` from end of event (#21223) We don't need this anymore because we flush in a microtask. This should allow us to remove the logic in the event system that tracks nested event dispatches. I added a test to confirm that nested event dispatches don't triggger a synchronous flush, like they would if we wrapped them `flushSync`. It already passed; I added it to prevent a regression.
commit sha bd7f4a013be3ef272a01874532bee71ad861e617
Fix sloppy factoring in `performSyncWorkOnRoot` (#21246) * Warn if `finishedLanes` is empty in commit phase See #21233 for context. * Fix sloppy factoring when assigning finishedLanes `finishedLanes` is assigned in `performSyncWorkOnRoot` and `performSyncWorkOnRoot`. It's meant to represent whichever lanes we used to render, but because of some sloppy factoring, it can sometimes equal `NoLanes`. The fixes are: - Always check if the lanes are not `NoLanes` before entering the work loop. There was a branch where this wasn't always true. - In `performSyncWorkOnRoot`, don't assume the next lanes are sync; the priority may have changed, or they may have been flushed by a previous task. - Don't re-assign the `lanes` variable (the one that gets assigned to `finishedLanes` until right before we enter the work loop, so that it is always corresponds to the newest complete root.
commit sha a632f7de3bd35eaf6d5082054af4da92dd37cf20
Flip tuple order of useTransition (#20976)
commit sha ef37d55b68ddc45d465b84ea2ce30e8328297b2d
Use performConcurrentWorkOnRoot for "sync default" (#21322) Instead of `performSyncWorkOnRoot`. The conceptual model is that the only difference between sync default updates (in React 18) and concurrent default updates (in a future major release) is time slicing. All other behavior should be the same (i.e. the stuff in `finishConcurrentRender`). Given this, I think it makes more sense to model the implementation this way, too. This exposed a quirk in the previous implementation where non-sync work was sometimes mistaken for sync work and flushed too early. In the new implementation, `performSyncWorkOnRoot` is only used for truly synchronous renders (i.e. `SyncLane`), which should make these mistakes less common. Fixes most of the tests marked with TODOs from #21072.
commit sha 89847bf6e6c0b77ced5dfc7b794c730bb3deac36
Continuous updates should interrupt transitions (#21323) Even when updates are sync by default. Discovered this quirk while working on #21322. Previously, when sync default updates are enabled, continuous updates are treated like default updates. We implemented this by assigning DefaultLane to continous updates. However, an unintended consequence of that approach is that continuous updates would no longer interrupt transitions, because default updates are not supposed to interrupt transitions. To fix this, I changed the implementation to always assign separate lanes for default and continuous updates. Then I entangle the lanes together.
commit sha a1558600183b4321d4cdc117925980f1865641fa
Fix: Don't flush discrete at end of batchedUpdates (#21229) The outermost `batchedUpdates` call flushes pending sync updates at the end. This was intended for legacy sync mode, but it also happens to flush discrete updates in concurrent mode. Instead, we should only flush sync updates at the end of `batchedUpdates` for legacy roots. Discrete sync updates can wait to flush in the microtask. `discreteUpdates` has the same issue, which is how I originally noticed this, but I'll change that one in a separate commit since it requires updating a few (no longer relevant) internal tests.
commit sha e8cdce40d667fa6745c9412b764c65eb85435b97
Don't flush sync at end of discreteUpdates (#21327) All it should do is change the priority. The updates will be flushed by the microtask.
commit sha af5037a7a8ee983337a08eeff7477656bd80f5ec
[Fizz] Wire up the Fixture (#21273) * Wire up fizz to fixture * Fixed typo conditional
commit sha 709f9484122f5913fcdf2520eab230dbb0ae6bd2
[Fizz] Add FB specific streaming API and build (#21337) Add FB specific streaming API and build
commit sha ad091759a949747f55e1bad498d19be884d4a654
Revert "Emit reactroot attribute on the first element we discover (#21154)" (#21340) This reverts commit 266c26ad45c977ecf67e9359809c37da1489ca63.
commit sha 9cd52b27fe7be3c320d1e94a016fc416e66569b1
Restore context after an error happens (#21341) Typically we don't need to restore the context here because we assume that we'll terminate the rest of the subtree so we don't need the correct context since we're not rendering any siblings. However, after a nested suspense boundary we need to restore the context. The boundary could do this but since we're already doing this in the suspense branch of renderNode, we might as well do it in the error case which isn't very perf sensitive anyway.
commit sha 0f5ebf366ea4eca2e6c6a652606af3218f12edd6
Delete unreferenced type (#21343) Had already deleted all the uses but didn't remove the type itself.
commit sha 48740429b4a74e984193e4e2d364d461e4fdc3be
Expiration: Do nothing except disable time slicing (#21345) We have a feature called "expiration" whose purpose is to prevent a concurrent update from being starved by higher priority events. If a lane is CPU-bound for too long, we finish the rest of the work synchronously without allowing further interruptions. In the current implementation, we do this in sort of a roundabout way: once a lane is determined to have expired, we entangle it with SyncLane and switch to the synchronous work loop. There are a few flaws with the approach. One is that SyncLane has a particular semantic meaning besides its non-yieldiness. For example, `flushSync` will force remaining Sync work to finish; currently, that also includes expired work, which isn't an intended behavior, but rather an artifact of the implementation. An event worse example is that passive effects triggered by a Sync update are flushed synchronously, before paint, so that its result is guaranteed to be observed by the next discrete event. But expired work has no such requirement: we're flushing expired effects before paint unnecessarily. Aside from the behaviorial implications, the current implementation has proven to be fragile: more than once, we've accidentally regressed performance due to a subtle change in how expiration is handled. This PR aims to radically simplify how we model starvation protection by scaling back the implementation as much as possible. In this new model, if a lane is expired, we disable time slicing. That's it. We don't entangle it with SyncLane. The only thing we do is skip the call to `shouldYield` in between each time slice. This is identical to how we model synchronous-by-default updates in React 18.
commit sha 84b9162cbe91a8c0169ec1171273be58f3a2398a
Use toMatchInlineSnapshot for dehydrated values (#20618)
commit sha 72123839450ac3344e03fb7caf5d295188214241
Enable strict effects mode for React Native Facebook builds (#21354)
commit sha fc33f12bdee1d0ffbcc83d25199cdf4d47252736
Remove unstable scheduler/tracing API (#20037)
push time in 3 days
delete branch kassens/relay-devtools
delete branch : dependabot/npm_and_yarn/dns-packet-1.3.4
delete time in 3 days
PR closed kassens/relay-devtools
Bumps dns-packet from 1.3.1 to 1.3.4. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/mafintosh/dns-packet/commit/ebdf849da5dc0d96836e87628349776c623c5be7"><code>ebdf849</code></a> 1.3.4</li> <li><a href="https://github.com/mafintosh/dns-packet/commit/ac578722f2707310b841b65aae61d6332f8882a1"><code>ac57872</code></a> move all allocUnsafes to allocs for easier maintenance</li> <li><a href="https://github.com/mafintosh/dns-packet/commit/c64c9507e51532c9e9a3cbefa146a134ecc025fd"><code>c64c950</code></a> 1.3.3</li> <li><a href="https://github.com/mafintosh/dns-packet/commit/0598ba19d18da4568b32415e60a9629061b3c45c"><code>0598ba1</code></a> fix .. in encodingLength</li> <li><a href="https://github.com/mafintosh/dns-packet/commit/010aedb33c1ee8c3f558db5249c1d46e2bd7a101"><code>010aedb</code></a> 1.3.2</li> <li><a href="https://github.com/mafintosh/dns-packet/commit/0d0d593f8df4e2712c43957a6c62e95047f12b2d"><code>0d0d593</code></a> backport encodingLength fix to v1</li> <li>See full diff in <a href="https://github.com/mafintosh/dns-packet/compare/v1.3.1...v1.3.4">compare view</a></li> </ul> </details> <br />
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
<details> <summary>Dependabot commands and options</summary> <br />
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
</details>
pr closed time in 3 days
pull request commentkassens/relay-devtools
Bump dns-packet from 1.3.1 to 1.3.4
Looks like dns-packet is up-to-date now, so this is no longer needed.
comment created time in 3 days
delete branch relayjs/relay-devtools
delete branch : dependabot/npm_and_yarn/dns-packet-1.3.4
delete time in 3 days