fix: type correction for loading, loadingIndicator, transpile

[wattanx]

🔗 Linked issue

Fixes: #1019
Fixes: #1016

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

I will correct the types for loading, loadingIndicator, transpile in the nuxt.config.
I would like to add type tests in a separate PR.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[yanniznik]

Nice <3

[wJoenn]

It's still missing the type false isn't it ?

[wattanx]

I have confirmed that setting false does not cause an error, what do you think is the problem?

[wJoenn]

Here's the current issue I have

And here's the attribute in the node_modules/@nuxt/bridge-schema/dist/index.d.ts ConfigSchema interface

 /**
  * Used to set the default properties of the page transitions.
  * 
  * You can either pass a string (the transition name) or an object with properties to bind to the `<Transition>` component that will wrap your pages.
  * 
  * 
  * @see [vue@2 documentation](https://v2.vuejs.org/v2/guide/transitions.html)
  * 
  * @see [vue@3 documentation](https://vuejs.org/guide/built-ins/transition-group.html#enter-leave-transitions)
 */
 pageTransition: {
  [key: string]: any
 },

[wJoenn]

@danielroe I just discovered another type mismatch (currently installing bridge on a old Nuxt 2 app).
app.meta.script raises an error when a body: true attribute is passed to a script

app: {
  head: {
    script: [
      { src: `https://polyfill.io/v3/polyfill.min.js?features=${POLYFILL_FEATURES}`, body: true }
    ]
  }
}

But I can see in Unhead's documentation that

Providing body: true is the same as tagPosition: 'bodyClose'

tagPosition: 'bodyClose' does not raise an error. body: true does.

Shall I open a new issue for this one ?