This website requires JavaScript.
About
Status
₊˚⊹Discord
Explore
Register
Sign in
Reference in a new issue
Blame
Copy permalink
Reference in a new issue
Copy permalink
TanStack
/
router
Star
0
Fork
You've already forked router
0
mirror of
https://github.com/TanStack/router.git
synced
2026-11-16 19:38:07 +00:00
Code
Issues
Releases
Packages
Activity
createFileRoute-without-path
router
/
examples
/
react
/
start-basic-react-query
/
app
/
api.ts
6 lines
165 B
Raw
Permalink
Normal View
History
feat(start): add api routes (#2185) * feat: partial work on file based api routes * feat(router-generator,start): tsr config to support `apiBase` * feat(router-generator): adding the route template * feat(router-generator): smoke test to make sure no conflicting configurations are found * chore(start-basic): cleanup to a workable state * feat(router-generator): generate the manifest for api-routes * feat(start): make sure requests are getting through * fix(react-router,start): get the exports sorted * refactor(router-generator): to use the same output as normal route files * feat(start): piping the manifest to the api-handler * chore(start): remove unused config option since the apiBase is being taken from tsr-generator * fix(start): only add the api router to vinxi if its handler exists * style(start): eslint * test(router-generator): checking that the custom base is respected by the generator * chore(start): add a dot notated api route and `console.debug` instead * refactor(router-generator,start): normalize the capitalization of "API" across the generator and start * fix(start): `createAPIHandler` to `createApiHandler` * feat(router-generator,start): correctly output the api build chunks * feat(start): 🎉 API-routes are working now it just needs Tanner's multi-sort logic stuff added-in * fix(start,router-generator): split the API stuff from the "server" export to its own "api"export * feat(router-generator): handle updating the path `escapedPath` on API-Routes like we do for regular file-routes * refactor(router-generator,start): rename functions * feat(start): add logic for route matching with TSR routes * feat(react-router,router-generator,start): remove the stuff to do with generating the "api-manifest". only the existing "route-manifest" remains. the additional tests have also been removed * fix(start): filter out potential api-route mismatches before trying to begin the actually "find" process * test: start-basic example with api routes * chore: add a DEPLOY_URL field to better show that the user needs to supply this SSR * test: start-basic-react-query example with api routes * chore: rename "post" to "user" * feat(start): allow the HTTP "HEAD" method * feat(start): solution for code-based api-routes * revert(start): undo the code-based approach since the production builds didn't work * feat(start): add back the code-based approach * chore(start): rename type "APIFileRouteReturnType" to "APIRouteReturnType" * fix(start): path logic to make sure url segments cannot be less than route segments * refactor(start): code-based approach to accept a an object of routes keyed under "routes" * chore(start): add comments since * refactor(router-generator,start): less exports and reuse make the fs-router extensible * refactor(start): a more generic name * refactor(start): generic naming again * refactor(start): strongly type the api handlers * docs(router): update the file-based routing to callout that `/api` routes will be ignored by router * docs(router): callout how the `api_base can be changed` --------- Co-authored-by: SeanCassiere <33615041+SeanCassiere@users.noreply.github.com>
2024-08-27 01:46:20 -06:00
fix: move to react-start (#3573)
2025-02-26 11:16:23 +01:00
feat(start): add api routes (#2185) * feat: partial work on file based api routes * feat(router-generator,start): tsr config to support `apiBase` * feat(router-generator): adding the route template * feat(router-generator): smoke test to make sure no conflicting configurations are found * chore(start-basic): cleanup to a workable state * feat(router-generator): generate the manifest for api-routes * feat(start): make sure requests are getting through * fix(react-router,start): get the exports sorted * refactor(router-generator): to use the same output as normal route files * feat(start): piping the manifest to the api-handler * chore(start): remove unused config option since the apiBase is being taken from tsr-generator * fix(start): only add the api router to vinxi if its handler exists * style(start): eslint * test(router-generator): checking that the custom base is respected by the generator * chore(start): add a dot notated api route and `console.debug` instead * refactor(router-generator,start): normalize the capitalization of "API" across the generator and start * fix(start): `createAPIHandler` to `createApiHandler` * feat(router-generator,start): correctly output the api build chunks * feat(start): 🎉 API-routes are working now it just needs Tanner's multi-sort logic stuff added-in * fix(start,router-generator): split the API stuff from the "server" export to its own "api"export * feat(router-generator): handle updating the path `escapedPath` on API-Routes like we do for regular file-routes * refactor(router-generator,start): rename functions * feat(start): add logic for route matching with TSR routes * feat(react-router,router-generator,start): remove the stuff to do with generating the "api-manifest". only the existing "route-manifest" remains. the additional tests have also been removed * fix(start): filter out potential api-route mismatches before trying to begin the actually "find" process * test: start-basic example with api routes * chore: add a DEPLOY_URL field to better show that the user needs to supply this SSR * test: start-basic-react-query example with api routes * chore: rename "post" to "user" * feat(start): allow the HTTP "HEAD" method * feat(start): solution for code-based api-routes * revert(start): undo the code-based approach since the production builds didn't work * feat(start): add back the code-based approach * chore(start): rename type "APIFileRouteReturnType" to "APIRouteReturnType" * fix(start): path logic to make sure url segments cannot be less than route segments * refactor(start): code-based approach to accept a an object of routes keyed under "routes" * chore(start): add comments since * refactor(router-generator,start): less exports and reuse make the fs-router extensible * refactor(start): a more generic name * refactor(start): generic naming again * refactor(start): strongly type the api handlers * docs(router): update the file-based routing to callout that `/api` routes will be ignored by router * docs(router): callout how the `api_base can be changed` --------- Co-authored-by: SeanCassiere <33615041+SeanCassiere@users.noreply.github.com>
2024-08-27 01:46:20 -06:00