[Bug] v11.0.0 usage problems

[neo-reply-lukas]

When upgrading to v11.0.0, imports in our project break.
That's because with the new build, the package is imported as CJS as default as opposed to es5 Module.

In the built package.json the following 'exports' option should be added. That way, the es5 module would be used for all import statements by default

{
  "main": "dist/fsxa-proxy-api.cjs.js",  // CJS version
  "module": "dist/fsxa-proxy-api.es5.js", // ES5/ESM version
  "exports": {
    ".": {
      "import": "./dist/fsxa-proxy-api.es5.js",
      "require": "./dist/fsxa-proxy-api.cjs.js"
    }
  }
}

[nico-mcalley]

Hi Lukas!

I see that you are experiencing the issue described with the “fsxa-proxy-api” package.
We did not see this behavior on v11.0.0.

I have a few questions about this:

1. Your problem only affects imports from “fsxa-proxy-api” – are imports from the “fsxa-api” package stable for you?
2. Have you already used “fsxa-proxy-api” in previous versions?
3. Could you provide a small reproduction that still works with v10.x and breakes with v11?
4. Could you check out the branch, build the fsxa-proxy-api locally, and check if that solves the problem?
   https://github.com/e-Spirit/javascript-content-api-library/blob/feat/PX368-export-as-esm/proxy/package.json

Thank you very much!
Best regards

Nico