fix: resolve TypeScript build error in projects using `--isolatedModules`

[alexandrutasica]

Types of changes

• [ ] Chore (a non-breaking change which is related to package maintenance)
• [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

Fixing issue when using Next.JS with Typescript with the mandatory --isolatedModule set to true. This requires having all type exports as export type. The change also keeps the type export consistent with the index.ts type exports. Fixes: Type error: Re-exporting a type when the '--isolatedModules' flag is provided requires using 'export type'.

Checklist:

• [ ] My change requires an update to the official documentation.
• [x] All TSDoc comments are up-to-date and new ones have been added where necessary.
• [x] All new and existing tests are passing.

🚘

[alexandrutasica]

@angeloashmore Noticed in a project of mine with Next.js, which requires --isolatedModule set to true, after updating to @prismicio/client v7. After the Migration Guide changes, Eslint returns errors for @prismicio/react:

Type error: Re-exporting a type when the '--isolatedModules' flag is provided requires using 'export type'.

The change also keeps it consistent with index.ts for exporting types. Not a groundbreaking bugs, but surely will help others with the same issue.

[angeloashmore]

Thanks for the fix, @alexandrutasica!

This has been released in v2.7.3.