compatibility mode not accurately emulating IE.

I changed our local es-dev-server to use build files from rollup and am getting errors with the legacy version loading in IE 11. I’d suggest we change es-dev-server to act like angular’s local dev server that compiles source files and outputs everything.

Aditionally, I have an error with my build output where the following error appears in IE when I import the component.

Unhandled promise rejection TypeError: @@toPrimitive must return a primitive value.

I am bundling chart.js which is just an import inside my web component. The chartjs import is a bundled file from another rollup output by the author. Anybody know how I can ignore my rollup configuration from ignoring and rollup transformations on that and just adding it to the output?

Following is my rollup config:

// import createDefaultConfig from '@open-wc/building-rollup/modern-and-legacy-config';
import { createCompatibilityConfig } from '@open-wc/building-rollup';
import replace from 'rollup-plugin-replace';
import typescript from '@rollup/plugin-typescript';
import babel from 'rollup-plugin-babel';
// if you need to support IE11 use 'modern-and-legacy-config' instead.
// import createDefaultConfig from '@open-wc/building-rollup/modern-and-legacy-config';

const configs = createCompatibilityConfig({
  production: true,
  input: './index.html',
  outputDir: 'dist-dev',
  plugins: [
    replace({
      'process.env.NODE_ENV': 'production',
    }),
    babel({}),
    typescript(),
  ],
  extensions: ['.js', '.ts', '.mjs'],
});

export default configs.map(config => ({
  ...config,
  output: {
    ...config.output,
    entryFileNames: '[name].js',
    chunkFileNames: '[name].js',
  },
}));

[LarsDenBakker]

Thanks a lot for that clarification

[LarsDenBakker]

Going to close this one as there isn’t an actionable item for us here.