fix(bundle): fix mixed exports issue

[eunjae-lee]

Summary

fixes #222

This PR fixes the mixed exports issue.
Since 7880205, search-insights started to have both default export and named exports.
There is an issue related to this in rollup.

I ended up modifying the bundle output.

from

exports.createInsightsClient=createInsightsClient;
exports.default=node

to

module.exports=node;
module.exports.createInsightsClient=createInsightsClient;

I couldn't find any elegant way to fix this other than this.

Result

All of the following works fine.

const aa = require("search-insights");

const { createInsightsClient } = require("search-insights");

import aa, { createInsightsClient } from "search-insights";

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 304e924:

Sandbox	Source
Vanilla	Configuration

[Haroenv]

This seems fine. I guess babel is no option, since it's rollup creating the exports and not babel?

Would we be able to create an entry point which is already cjs to conform to the shape from the start?

[eunjae-lee]

This seems fine. I guess babel is no option, since it's rollup creating the exports and not babel?

Would we be able to create an entry point which is already cjs to conform to the shape from the start?

Didn't think of that!
WDYT 304e924 ?