Add export field to package.json

[steciuk]

When the export field is missing vitest is using CommonJS version of the package even if the module key is specified which leads to problems with importing vitest from inside the package in a ESM project.

For example using:

chrome.runtime.connect('test');

leads to:

TypeError: Cannot read properties of undefined (reading 'fn')
 ❯ addFunction node_modules/vitest-chrome/src/add-elements.ts:73:12
 ❯ Object.get node_modules/vitest-chrome/src/createHandler.ts:64:20

See: vitest-dev/vitest#4233

[DanielRivers]

Would love for this to be merged.

[frontendphil]

I was literally about to open the exact same PR. This would be great!

[fregante]

Since this package is abandoned, here's the fix:

import { defineConfig } from 'vitest/config';

export default defineConfig({
  test: {
    setupFiles: ['./source/vitest.setup.js'],
  },
  resolve: {
    alias: {
      'vitest-chrome': import.meta.resolve('vitest-chrome/lib/index.esm.js'),
    },
  },
});

and then place this in your setup file:

import {chrome} from 'vitest-chrome';

globalThis.chrome = chrome;