When invalid syntax is used in definePage() calls, the Vite dev server would crash instead of gracefully handling the error. This happened because parsing errors from Babel were not caught and would bubble up, terminating the development server.

For example, this invalid syntax would crash the server:

<script setup lang="ts">
definePage({ 2, 3 }) // syntax error by accident
</script>

Changes made:

• Added comprehensive error handling in getCodeAst() function to catch parsing errors from babelParse() and Vue SFC parsing methods
• When syntax errors occur:
  • Normal transform returns undefined to skip processing
  • DefinePage extraction returns 'export default {}' as a safe fallback
  • Logs a warning message instead of crashing
• Both definePageTransform() and extractDefinePageNameAndPath() now handle errors gracefully
• Added comprehensive test coverage for various syntax error scenarios

The fix ensures that developers can continue working even when they accidentally introduce syntax errors in definePage() calls, while preserving all existing functionality for valid code.

Fixes #691.

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.