Add indexer object to config defaults

[digbyk]

Added empty indexer object to defaults to prevent error on startup on line 153 when no indexer is present in nuxt.config.ts

I noticed when upgrading to 1.0.0 that the module wouldn't load unless an indexer object was present in nuxt.config, giving the following error: Cannot start nuxt: Cannot convert undefined or null to object
at Function.keys () at setup (/.../node_modules/@nuxtjs/algolia/dist/module.mjs:174:16)

Types of changes

• [ x ] Bug fix (a non-breaking change which fixes an issue)
• [ ] New feature (a non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

This fixes the error described above. I means you don't need an indexer object in the nuxt.config when one isn't needed.

Checklist:

• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [ ] I have added tests to cover my changes (if not applicable, please state why)

[netlify[bot]]

✅ Deploy Preview for nuxt-algolia-module canceled.

Name	Link
🔨 Latest commit	00404f3f8e28d1582b9ed25ac3eb76b0af3e9e5d
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt-algolia-module/deploys/62bde4e64ac36c0009e0c532

[Baroshem]

Hey @digbyk

Sorry for no contact from my side. I completely missed this PR. For some reason, PR's are not appearing in my notifications in Github, while reported issues are there normally.

I fixed this issue another way in the 1.0.1 version so it should not appear anymore. I basically added a check that if there no config object was provided it should not try to convert it to object. It fixed the issue as well

I will merge your code as well. It wont break anything but can add another safety layer to the configuration :)

[Baroshem]

I will merge it and release it with 1.1.0 that will be release in few weeks probably :)

[digbyk]

Great. Thanks for letting me know. Kudos for all your hard work on this.