content(blog): article migration React Router v7 + tweak défense en profondeur#43
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contenu
Deux articles de blog :
migration-remix-react-router-v7.mdx(nouveau) — retour d'expérience sur la migration Remix v2 → React Router v7, déclenchée par unnpm audità 15 vulnérabilités. Packages, entry files, config Vite (piège d'ordre MDX/reactRouter),react-router.config.ts, typegen, scripts npm, vérif route par route.defense-en-profondeur-self-host.mdx— petit ajustement (1 ligne).Notes éditoriales
Deux ajustements mineurs sur le nouvel article pour coller au reste du blog :
slug(le slug vient du nom de fichier, aucun autre article ne l'a), ajout dereadingTime: 8etdraft: false.[le mien est ici](#)(ancre morte) a été retiré de la conclusion pour éviter un lien cassé. À remplacer par l'URL du commit/PR de migration si tu veux le réintroduire.Build vérifié en local (
npm run build→ exit 0, les deux articles sont bien pris en compte).