-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Add routes.ts
support behind future flag
#10107
Conversation
🦋 Changeset detectedLatest commit: 5f98394 The changes in this PR will be included in the next version bump. This PR includes changesets to release 19 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 |
routes.ts
routes.ts
export type { | ||
DefineRoutesFunction as UNSAFE_DefineRoutesFunction, | ||
RouteManifest as UNSAFE_RouteManifest, | ||
RouteManifestEntry as UNSAFE_RouteManifestEntry, | ||
RouteConfig as UNSAFE_RouteConfig, | ||
RouteConfigEntry as UNSAFE_RouteConfigEntry, | ||
} from "./config/routes"; | ||
export { | ||
defineRoutes as UNSAFE_defineRoutes, | ||
routeManifestToRouteConfig as UNSAFE_routeManifestToRouteConfig, | ||
getRouteConfigAppDirectory as UNSAFE_getRouteConfigAppDirectory, | ||
} from "./config/routes"; | ||
export { flatRoutes as UNSAFE_flatRoutes } from "./config/flat-routes"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This isn't needed in React Router because @remix-run/dev/routes
has access to the internals of the dev package, whereas in this case we need to expose these internals across package boundaries.
routes.ts
routes.ts
support behind future flag
🤖 Hello there, We just published version Thanks! |
See changeset and docs for more details.