Releases: oedotme/generouted
Releases · oedotme/generouted
v1.14.0
Changes
You can now export an app level error boundary Catch
component from src/pages/_app.tsx
with the following integrations:
@generouted/react-router
,@generouted/react-router/lazy
// src/pages/_app.tsx
export const Catch = () => <div>...</div>
@generouted/solid-router
,@generouted/solid-router/lazy
// src/pages/_app.tsx
export const Catch = (props: { error: Error; reset: () => void }) => <div>...</div>
Breaking changes 🚨
If you're using the generatePreservedRoutes
directly from the core functions or through a custom integration you should now access the default
export explicitly:
const preservedRoutes = generatePreservedRoutes(PRESERVED)
-const App = preservedRoutes?.['_app'] || Outlet
-const NotFound = preservedRoutes?.['404'] || Fragment
+const App = preservedRoutes?.['_app']?.default || Outlet
+const NotFound = preservedRoutes?.['404']?.default || Fragment
Commits
Changelog: v1.13.7...v1.14.0
v1.13.7
Changes
- Setup issue template
- Updated docs structure, content and conventions example
- Add file-based
Catch
component with error boundary for Solid integrations
export const Catch = (props: { error: Error; reset: () => void }) => <div>...</div>
Commits
- chore: update packages d85724d by @oedotme
- docs: remove src/pages from conventions example table b374b0f by @oedotme
- docs: update logo size 19d01aa by @oedotme
- docs: move experimental and deprecated integrations to the bottom 8c034ff by @oedotme
- docs: update readme structure and content e6e9d07 by @oedotme
- feat: add catch component w/ error boundary for solid-router a1758bb by @oedotme
- docs: add simple custom react-router example 5c88344 by @oedotme
- docs: update react-router custom example path 2b55dc2 by @oedotme
- chore: setup issue template 6b31a97 by @oedotme
Changelog: v1.13.6...v1.13.7
v1.13.6
v1.13.5
v1.13.4
v1.13.3
v1.13.2
v1.13.1
v1.13.0
Changes
- Support option for nested
src/pages
in nested directory such asclient/src/pages
orapps/dashboard/src/pages
- Custom integration full example
- Auto-format generated
router.ts
file with prettier by default if prettier is installed
Breaking changes at Vite plugin options
source
is now an object instead of string to accept bothroutes
andmodals
patternsoutput
is now the full output file path instead of only file name
// default values when using `generouted()` plugin with no options (recommended)
{
source: { routes: './src/pages/**/[\\w[-]*.{jsx,tsx}', modals: './src/pages/**/[+]*.{jsx,tsx}' },
output: './src/router.ts',
format: true,
}
Commits
- docs: update custom integration stackblitz link 8988e9c by @oedotme
- chore: update packages 7fad487 by @oedotme
- docs: add custom integration example 1e7db9b by @oedotme
- feat: optionally auto format router.ts with prettier 5bc491a by @oedotme
- feat: option for nested src/pages as client/src/pages e0a5593 by @oedotme closes #73, #90
- test: add ignored files to regular routes cases 0c951db by @oedotme
- test: base cases for core functions 54d5439 by @oedotme
- chore: build dependencies first with turbo build c0c360c by @oedotme
- chore: update packages ec99941 by @oedotme
- test: setup vitest 0267feb by @oedotme
Changelog: v1.12.9...v1.13.0