[question] Usage of Excel export with CSP header

[Jul13nT]

Order ID

69724

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

The problem in depth 🔍

I'm trying to use the Excel export feature with the premium Data Grid. My application is deployed with a NGINX server which adds a CSP header with script-src 'self';. When using the export, the script is blocked by the CSP header because of a Function instruction.

I traced the cause to the library regenerator-runtime, used by ExcelJS. This seems to be a known issue: exceljs/exceljs#713 and facebook/regenerator#378 (comment)

I use vite to build my application, I managed to "fix" the problem by adding this to the vite config:

build: {
    rollupOptions: {
        output: {
            intro: 'window.regeneratorRuntime = undefined;',
        },
    },
},

My question is: have you ever encountered this problem and do you have a better solution to solve it?

Your environment 🌎

`npx @mui/envinfo`

  System:
    OS: Linux 5.19 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
  Binaries:
    Node: 18.16.1 - /usr/bin/node
    Yarn: 3.2.4 - /usr/bin/yarn
    npm: 9.5.1 - /usr/bin/npm
  Browsers:
    Chrome: 114.0.5735.198

[m4theushw]

Answering the question, we've not encountered this issue before because the Excel feature was tested in the docs website, which uses Next.js. I'll keep this issue open in case someone also has this problem, but we don't have a better solution for now.

[cherniavskii]

Closing in favor of #11153

[github-actions]

⚠️ This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.

@Jul13nT: How did we do? Your experience with our support team matters to us. If you have a moment, please share your thoughts in this short Support Satisfaction survey.