-
-
Notifications
You must be signed in to change notification settings - Fork 579
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: 856872c 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 856872c
☁️ 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? |
The leaf packages (i.e
@tanstack/react-form-devtools) being pointed at the same import for development, causes issues when building the devtools for production.Since, the panel and plugin in React package point their imports at the apex of the root package (
form-devtool), and not the/productionbranch, it means that whenever a production build is initiated, the export conditions for production in the form devtools core package are never hit, which in turn erases the panel from being present in production.Closes #1986
🎯 Changes
✅ Checklist
pnpm test:pr.🚀 Release Impact