* Use stable release in demos with HTML output
* Fix Activity sandboxes (#8035)
* Fix Activity sandboxes
* hacky fix
* Revert "Fix Activity sandboxes (#8035)"
This reverts commit f9fd07ca59.
* Bump to 19.2
* cleanup rest of sandpacks
* Pin deps
* Add back package.json with third-party deps
* "^" should be fixed now
* add back package.json for more toastify deps
* fuggin whitespace
* more fuggin whitespace
* fml like fr fr
---------
Co-authored-by: Sebastian Sebbie Silbermann <sebastian.silbermann@vercel.com>
Co-authored-by: Ricky <rickhanlonii@gmail.com>
Co-authored-by: Rick Hanlon <rickhanlonii@meta.com>
We're updating eslint-plugin-react-hooks with support for useEffectEvent usage and updated configuration options for applying the useEffectEvent and other effect rules to custom effect hooks.
This adds the documentation for the config syntax and adds mention to the useEffectEvent reference page that the linter should be used to ensure proper usage of Effect Events.
* docs: scaffold docs structure for Performance tracks
* docs: initial draft of Tracks section
* refactor: moved to reference root section and added to the sidebar
* chore: updated to canary and minor changes
* Docs for `cacheSignal`
* Apply suggestion from review
Co-authored-by: Sebastian Markbåge <sebastian@calyptus.eu>
* Apply suggestion from review
Co-authored-by: Sebastian Markbåge <sebastian@calyptus.eu>
* Update src/content/reference/react/cacheSignal.md
---------
Co-authored-by: Sebastian Markbåge <sebastian@calyptus.eu>
For local dev and CI we want to have the eslint-local-rules running, so let's make sure both have their dependencies installed. We don't use a monorepo setup here, which is why they're currently setup as a two completely independent yarn workspaces.
Previously, `createFileMap` split the MDX meta string on spaces and assumed the first token was the filename. Once we prefixed code fences with `{expectedErrors: ...}`, it would incorrectly parse the meta and crash.
This PR updates createFileMap to skip tokens in the meta containing a start and end brace pair (using a stack to ensure we close on the correct brace) while tokenizing the meta string as expected.
Test plan: pages reported in #7994 no longer crash on the next PR
Closes#7994
Previously, `createFileMap` split the MDX meta string on spaces and assumed the first token was the filename. Once we prefixed code fences with `{expectedErrors: ...}`, it would incorrectly parse the meta and crash.
This PR updates createFileMap to skip tokens in the meta containing a start and end brace pair (using a stack to ensure we close on the correct brace) while tokenizing the meta string as expected.
Test plan: pages reported in #7994 no longer crash on the next PR
Closes#7994
Previously, `createFileMap` split the MDX meta string on spaces and assumed the first token was the filename. Once we prefixed code fences with `{expectedErrors: ...}`, it would incorrectly parse the meta and crash.
This PR updates createFileMap to skip tokens in the meta containing a start and end brace pair (using a stack to ensure we close on the correct brace) while tokenizing the meta string as expected.
Test plan: pages reported in #7994 no longer crash on the next PR
Closes#7994
Reverts the revert now that we've fixed the bug. These pages should no longer crash:
/learn/referencing-values-with-refs
/learn/synchronizing-with-effects
/learn/separating-events-from-effects
/learn/removing-effect-dependencies
Previously, `createFileMap` split the MDX meta string on spaces and assumed the first token was the filename. Once we prefixed code fences with `{expectedErrors: …}`, it would incorrectly parse the meta and crash.
This PR updates createFileMap to skip tokens in the meta containing a start and end brace pair (using a stack to ensure we close on the correct brace) while tokenizing the meta string as expected.
I also added a fallback that was previously not handled if the filepath was undefined.
Test plan: pages reported in #7994 no longer crash on the next PR
Closes#7994
