fix(type-defs): make all options optional

[jankal]

When using the module with a typed nuxt.config.ts, TypeScript requires all properties of the options object to be set.
They don't have to, because the defaults will be used if they are not set.

[codecov]

Codecov Report

Merging #56 (312d781) into master (2867137) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #56   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         2           
  Lines           20        20           
  Branches         3         3           
=========================================
  Hits            20        20           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2867137...312d781. Read the comment docs.

[pi0]

We may also use Partial<{}>

[jankal]

@pi0 Thanks for that! Didn't think of it. Do you think it would be better / more consistent with other packages to adjust it? - If so, I will do. The definite pro is that you don't have to think about the question-mark on each property. A con would be the possible introduction of required properties in the future.

[pi0]

Common convention for nuxt config is:

• Defining an XOptions interface with all props required (considering defaults applied)
• Defining XConfig = Partial<XOptions> for user input

Advantages:

• When writing internals, we are sure defaults always being applied
• No duplicate types for input and internal options
• Ensure module remains zero config (and if a prop is really required, is checked on runtime js)

[atinux]

Thanks @jankal and @pi0, will release patch now :)