- Script de generation de typage des evenements et de propriétés basé sur un CSV ou une API si votre outil le permet
- nomenclature de nommages des events
- nomenclature de nommage des propriétés d'event
- Une seule source de confiance des events
- Générer le fichier de typage dans la CI pour verif

Despite these challenges, Capacitor remains a solid choice for web-first applications that need a unified experience across platforms.
👉 If you’ve built a large-scale app with Capacitor, what were your biggest challenges? Let’s discuss! 🚀

- Implementation time → For a large-scale application, properly stabilizing a Capacitor-based app can take 4 to 6 months of development to ensure performance, reliable plugin integration, and feature consistency across platforms

-Offline support & caching can be challenging → Persistent storage and offline capabilities aren’t as seamless as with native solutions.

-Debugging complexity → Testing and debugging across web, iOS, and Android can introduce unexpected edge cases due to WebView behavior.

- Performance trade-offs → Capacitor provides near-native performance, but heavy applications or complex UI interactions may introduce inconsistencies/lag compared to native frameworks.

-Plugin ecosystem limitations→ While Cap. supports sev native features, some rely on 3rd-party plugins, which may not always be well-maintained/optimized for perf

Push notifications/background tasks require extra setup→ Managing these efficiently requires additional config/potential workarounds

- Page transitions in web-based navigation can be tedious and require extra effort to get right

- WebView constraints→ Unlike native apps, web-based applications face browser-imposed limitations. For example, gesture-based navigation often feels less natural compared to fully native implementations

- Certain features are not well-handled → For instance, setTimeout, which is crucial for background tasks, can be unreliable.

- Crafting a "React Native-like" experience requires planning → Smooth animations, app fluidity, and rethinking design system components are essential before committing.

While Capacitor is a solid solution, there are some key considerations to keep in mind before making the switch:

- Dual compatibility overhead → Any modification on Android needs to be checked for backward compatibility across browsers and mobile OSs.

But musk fail

La doc de BiomeJS et sa facilité de setup est vraiment sympa. On a pas encore un linter assez propre sur les fichiers CSS quand ils sont mixés avec des variables Tailwind, pas de lint sur MDX mais dans la roadmap de Biome en 2025.

BiomeJS vs ESLint => La différence de performance entre les deux est insane.
Sur 2k2 files en JS TS Graphql je suis a une moyenne de 1 min de lint avec ESLint et ... DEUX SECONDES sur BiomeJS. Dé-li-rant. Merci le rust.

importante sur la plateforme selon la quantité de breaking change. Il n'empeche que l'IA facilite grandement la migration vers de nouveaux outils, pas trop nouveau non plus parce qu'ils ne sont pas suffisamment rapide sur leur mise à jour encore.