[0.8.x] Custom PageNotFoundError for resolvePageComponent

[RobertBoes]

Currently a generic Error is thrown in resolvePageComponent, this PR changes that to a PageNotFoundError. This is particularly useful for projects that use React and want to transition from JS to TS. With this change it would be easier to load components from different locations/paths, or different file types such as jsx and tsx. With the custom exception it's a lot easier to check if the component doesn't exist or if it's another kind of error. An example in Inertia might look something like this:

import { createInertiaApp } from '@inertiajs/react'
import { resolvePageComponent, PageNotFoundError } from 'laravel-vite-plugin/inertia-helpers';
 
createInertiaApp({
  resolve: async (name) => {
    try {
      return await resolvePageComponent(`./Pages/${name}.jsx`, import.meta.glob('./Pages/**/*.jsx'))
    } catch (e) {
      if (e instanceof PageNotFoundError) {
        return await resolvePageComponent(`./Pages/${name}.tsx`, import.meta.glob('./Pages/**/*.tsx'))
      }

      throw e
    }
  }
  // ...
})

[timacdonald]

Thanks for the PR.

I think we might be able to solve this via #252, where you could pass a callback as the last parameter to determine what to do when no page is able to be found.

This would give you a first party way of doing what you are trying to do here, but without the need for the named exception / try catch.

Thoughts?

We can probably still throw a named error, though.

[timacdonald]

Thanks so much for this feature. I've merged the changes into this related PR: #252