-
-
Notifications
You must be signed in to change notification settings - Fork 580
devtools move production exports to dedicated subdirectory #1989
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 10fc53e The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
View your CI Pipeline Execution ↗ for commit 10fc53e
☁️ Nx Cloud last updated this comment at |
|
This makes sense to me, can you add a change set to the PR? |
Moved production exports of devtools to a dedicated subdirectory.
|
@harry-whorlow should I apply these changes to the Solid devtools as well? |
|
If you would that would be awesome! 🔥 |
|
@harry-whorlow this is good to go 👍🏼 |
This PR makes changes to the code paths for the production exports of
@tanstack/react-form-devtoolsand@tanstack/solid-form-devtools.The previous implementation had the
productionexports sourcing the Form Devtools Panel component from thedevelopmentimport. This meant that on build of your app, the production export would work, without erroring-out, but when running it in the browser, the Devtools Panel for Form would just be empty/null.Closes #1986
🎯 Changes
✅ Checklist
pnpm test:pr.🚀 Release Impact