Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

webpack-preprocessor cleanError throws TypeError #8948

Closed
lenntt opened this issue Oct 23, 2020 · 51 comments
Closed

webpack-preprocessor cleanError throws TypeError #8948

lenntt opened this issue Oct 23, 2020 · 51 comments
Labels
prevent-stale mark an issue so it is ignored by stale[bot] stage: awaiting response Potential fix was proposed; awaiting response topic: preprocessors 🔧 type: bug

Comments

@lenntt
Copy link

lenntt commented Oct 23, 2020

return err.replace(/\n\s*at.*/g, '').replace(/From previous event:\n?/g, '')

TypeError: err.replace is not a function
It seems err is an Error in my case, not a string.

I'm not familiar enough to make sure it would break anything else, but changing the js output locally to err.message.replacefixes things for me.

My real error was:
"Module not found: Error: Can't resolve '../../src/Component' in '<mypath>/cypress/component'"

@kwuite
Copy link

kwuite commented Oct 30, 2020

+1 I have the exact same issue. Copy pasted example code from npm, used any example I could find but to no avail. It all ends with the same error.
image

@kwuite
Copy link

kwuite commented Oct 30, 2020

New package was released today by version 5.4.9 and the dist folder is completely empty.

Starting version 4.1.1 I get the err.replace is not a function.

This al feels very broken.

I need to fix webpack because currently even the most simplest of files are 6MB in size after compilation and it takes on average 4,5 second just to build it (not even importing it to the browser).

@epashkov

This comment has been minimized.

@epashkov
Copy link

There is no problems with webpack@4.44.2

@mkalam-alami
Copy link

mkalam-alami commented Nov 11, 2020

I got this error by upgrading to Webpack 5, which I cancelled for the time being. Does this bug mean @cypress/webpack-preprocessor does not support Webpack 5 yet, or is it something new?

Not sure if related but the preprocessor files have received some fairly recent changes which may have broken something.

(To the maintainers: in passing I've just come across some merge markers left in webpack.js https://github.com/cypress-io/cypress/blob/master/npm/vue/src/preprocessor/webpack.js#L79)

@cypress-bot cypress-bot bot added stage: ready for work The issue is reproducible and in scope and removed stage: work in progress labels Nov 13, 2020
@echenley
Copy link

echenley commented Nov 13, 2020

The underlying problem here seems to be that the webpack instance started by cypress is using a flawed require.resolve algorithm. You can use cypress-webpack-preprocessor-v5 to fix the err.replace error, but the underlying issue remains where the modules required by webpack dependencies are not using the normal node resolution algorithm.

In my case, babel-loader throws an error validateOptions is not a function because it is resolving the wrong version of schema-utils. I added some logs to the top of node_modules/babel-loader/lib/index.js to prove this:

console.log(require.resolve.paths('schema-utils'));
// [
//   <rootDir>/node_modules/babel-loader/node_modules
//   <rootDir>/node_modules
//   etc.
// ]
// ^ schema-utils is installed in both places, meaning it should resolve to the
// version located at babel-loader/node_modules/schema-utils

console.log(require.resolve('schema-utils'));
// <rootDir>/node_modules/schema-utils/dist/index.js
// ^ instead, it resolves to the version in <rootDir>/node_modules/schema-utils

I've also seen this same issue manifest with different versions of enhanced-resolve installed in node_modules/webpack/node_modules/enhanced-resolve and node_modules/enhanced-resolve. I would not be surprised if there are other variations of the same issue.

@har-preet

This comment has been minimized.

@chris-hmmr

This comment has been minimized.

@or2008

This comment has been minimized.

2 similar comments
@christopherread

This comment has been minimized.

@vranky

This comment has been minimized.

@mkalam-alami
Copy link

Please prefer thumbing up the issue over posting "+1" comments (each one of them sends unnecessary email notifications). Thanks

@sainthkh
Copy link
Contributor

sainthkh commented Dec 2, 2020

Can anyone provide a reproducible example? We cannot merge the code to the main branch without writing some test codes.

@sainthkh sainthkh added stage: awaiting response Potential fix was proposed; awaiting response and removed stage: ready for work The issue is reproducible and in scope labels Dec 2, 2020
@jennifer-shehane
Copy link
Member

Cypress webpack-preprocessor does not yet support Webpack 5 as explained in this issue: #8900

We released a temporary version of this package that supports webpack v5 – npmjs.com/package/cypress-webpack-preprocessor-v5

npm i cypress-webpack-preprocessor-v5

Is anyone getting this error outside of using Webpack 5? Because we will close this issue if not as it's a duplicate of #8900

@chris-hmmr
Copy link

Cypress webpack-preprocessor does not yet support Webpack 5 as explained in this issue: #8900

We released a temporary version of this package that supports webpack v5 – npmjs.com/package/cypress-webpack-preprocessor-v5

npm i cypress-webpack-preprocessor-v5

Is anyone getting this error outside of using Webpack 5? Because we will close this issue if not as it's a duplicate of #8900

Hi, using the cypress-webpack-preprocessor-v5 fixes the issue for me.

@ThaiChingChong
Copy link

ThaiChingChong commented Dec 17, 2020

Hi,
I am still facing the above issue after trying to install this package cypress-webpack-preprocessor-v5 . I am still seeing the following errors when I tried to run my tests.

The following error was thrown by a plugin. We stopped running your tests because a plugin crashed. Please check your plugins file 
TypeError: err.replace is not a function

My package.json dependancies

"devDependencies": {
    "@babel/core": "^7.12.10",
    "@babel/preset-env": "^7.12.11",
    "@cypress/webpack-preprocessor": "^5.5.0",
    "@newsint/nu-sun-linting": "^1.3.1",
    "@types/amphtml-validator": "^1.0.1",
    "@types/cypress-image-snapshot": "^3.1.2",
    "amphtml-validator": "^1.0.29",
    "babel-loader": "^8.2.2",
    "cypress": "^6.1.0",
    "cypress-image-snapshot": "^3.1.1",
    "cypress-wait-until": "^1.6.1",
    "fs": "0.0.1-security",
    "lint-staged": "7.2.2",
    "path": "^0.12.7",
    "tsify": "^4.0.1",
    "typescript": "3.8.3",
    "webpack": "^5.11.0"
  },

Am I missing something here?

@jennifer-shehane
Copy link
Member

@ThaiChingChong You need to install cypress-webpack-preprocessor-v5, this is not listed in your dev dependencies. Uninstall @cypress/webpack-preprocessor and install cypress-webpack-preprocessor-v5

{
  "devDependencies": {
    "cypress": "6.1.0",
    "cypress-webpack-preprocessor-v5": "^5.0.0-alpha.1"
  }
}

@ThaiChingChong
Copy link

@ThaiChingChong You need to install cypress-webpack-preprocessor-v5, this is not listed in your dev dependencies. Uninstall @cypress/webpack-preprocessor and install cypress-webpack-preprocessor-v5

{
  "devDependencies": {
    "cypress": "6.1.0",
    "cypress-webpack-preprocessor-v5": "^5.0.0-alpha.1"
  }
}

Thanks Jennifer. It's working fine now. I've uninstalled the original @cypress/webpack-preprocessor and reinstalled cypress-webpack-preprocessor-v5 and now I'm getting a different error when trying to launch Cypress tests. At least its a different errors now. :)

@Maleckidd
Copy link

Maleckidd commented Jan 7, 2021

@ThaiChingChong You need to install cypress-webpack-preprocessor-v5, this is not listed in your dev dependencies. Uninstall @cypress/webpack-preprocessor and install cypress-webpack-preprocessor-v5

{
  "devDependencies": {
    "cypress": "6.1.0",
    "cypress-webpack-preprocessor-v5": "^5.0.0-alpha.1"
  }
}

Hi Jeniffer. Similar problem here. Its occurs randomly. I have tried this solution but it didn't help.

Error message: Uncaught TypeError: display.replaceAll is not a function

"cypress": "4.0.2",
"webpack": "4.44.1",

@Donaab
Copy link

Donaab commented Jan 31, 2021

I have the same issue. I have installed cypress globally and I have installed dependancies from the project

{
    "name": "cypress-tests",
    "version": "0.1.0",
    "dependencies": {
        "@bahmutov/cy-api": "^1.4.2",
        "cypress-commands": "^1.1.0",
        "cypress-file-upload": "^4.0.7",
        "is-my-json-valid": "^2.20.4",
        "ts-loader": "^8.0.1",
        "typescript": "^4.1.2",
        "@typescript-eslint/parser": "^4.9.0",
        "@testing-library/cypress": "^7.0.2"
    }
}

I have tried with cypress 6.1.0 and 6.3.0. Also I have tried to install the mentioned cypress-webpack-preprocessor-v5 but I didn't use it before so I didn't add any other configuration for it like adding it to the plugins file etc.

@Donaab
Copy link

Donaab commented Jan 31, 2021

The underlying problem here seems to be that the webpack instance started by cypress is using a flawed require.resolve algorithm. You can use cypress-webpack-preprocessor-v5 to fix the err.replace error, but the underlying issue remains where the modules required by webpack dependencies are not using the normal node resolution algorithm.

In my case, babel-loader throws an error validateOptions is not a function because it is resolving the wrong version of schema-utils. I added some logs to the top of node_modules/babel-loader/lib/index.js to prove this:

console.log(require.resolve.paths('schema-utils'));
// [
//   <rootDir>/node_modules/babel-loader/node_modules
//   <rootDir>/node_modules
//   etc.
// ]
// ^ schema-utils is installed in both places, meaning it should resolve to the
// version located at babel-loader/node_modules/schema-utils

console.log(require.resolve('schema-utils'));
// <rootDir>/node_modules/schema-utils/dist/index.js
// ^ instead, it resolves to the version in <rootDir>/node_modules/schema-utils

I've also seen this same issue manifest with different versions of enhanced-resolve installed in node_modules/webpack/node_modules/enhanced-resolve and node_modules/enhanced-resolve. I would not be surprised if there are other variations of the same issue.

Yes got the same issue after the fixing TypeError: err.replace is not a function

@inspiraller
Copy link

@brandon-leapyear
Hi I'd like to try your solution. Can you elaborate on where you put this code? And where err.replace(..) exists?
regards

@inspiraller
Copy link

inspiraller commented May 12, 2021

actually I realise now I've edited this file directly in my node_modules folder:

node_modules/@cypress/webpack-preprocessor/dist.index.js
Adding line - console.log('err = ', err); // add this line

function cleanseError(err) {
    console.log('err = ', err); // add this line
    return err.replace(/\n\s*at.*/g, '').replace(/From previous event:\n?/g, '');
}

Now running cypress I can see the typescript errors I need to fix.
thankyou

@rkrisztian
Copy link

Opened nrwl/nx#5906 for nrwl/nx users, as I couldn't find a way to replace cypress-webpack-preprocessor with cypress-webpack-preprocessor-v5 there.

@msmith1114
Copy link

The underlying problem here seems to be that the webpack instance started by cypress is using a flawed require.resolve algorithm. You can use cypress-webpack-preprocessor-v5 to fix the err.replace error, but the underlying issue remains where the modules required by webpack dependencies are not using the normal node resolution algorithm.
In my case, babel-loader throws an error validateOptions is not a function because it is resolving the wrong version of schema-utils. I added some logs to the top of node_modules/babel-loader/lib/index.js to prove this:

console.log(require.resolve.paths('schema-utils'));
// [
//   <rootDir>/node_modules/babel-loader/node_modules
//   <rootDir>/node_modules
//   etc.
// ]
// ^ schema-utils is installed in both places, meaning it should resolve to the
// version located at babel-loader/node_modules/schema-utils

console.log(require.resolve('schema-utils'));
// <rootDir>/node_modules/schema-utils/dist/index.js
// ^ instead, it resolves to the version in <rootDir>/node_modules/schema-utils

I've also seen this same issue manifest with different versions of enhanced-resolve installed in node_modules/webpack/node_modules/enhanced-resolve and node_modules/enhanced-resolve. I would not be surprised if there are other variations of the same issue.

I'm facing this exact problem too in a project. This is not Webpack 5, but rather 4.46.0. I'm seeing this error:

TypeError: validateOptions is not a function at new SourceMapDevToolPlugin (~/code/project/node_modules/webpack/lib/SourceMapDevToolPlugin.js:107:3)

Logging out require.resolve and require.resolve.paths for schema-utils in SourceMapDevToolPlugin.js gives this:

console.log(require.resolve.paths('schema-utils'));
// [
//   '<rootDir>/node_modules/webpack/lib/node_modules',
//   '<rootDir>/node_modules/webpack/node_modules',
//   '<rootDir>/node_modules',
// 	 ...
// ]

console.log(require.resolve('schema-utils'));
// <rootDir>/node_modules/schema-utils/dist/index.js

Did you find a workaround, @echenley?

@jryom I am seeing the exact same validateOptions error as well, with the same webpack. Did you ever find a resolution?

@jryom
Copy link

jryom commented Jun 25, 2021

@msmith1114 for me the error went away after updating to Cypress 7.x 🤷

@JaoViana
Copy link

@jryom as for me.
Last week I use and was ok.
Today, this BS.
Any tips?

@inspiraller
Copy link

@krogfast
Its worth noting that whenever you do an npm install, if you have any custom plugins in cypress plugins folder they get overwritten. Check that hasn't happened and restore it if you had it working previously.

@JohnnyFun
Copy link

JohnnyFun commented Jul 16, 2021

This appears to be resolved in cypress as of version 7.6 #15447

UPDATE: spoke too soon. still get "Automatic publicPath is not supported in this browser" since the plugin doesn't allow me to override publicPath and set it to empty string.

@mhamri
Copy link

mhamri commented Jul 26, 2021

i'm facing the same issue, I put a console.log() to see what is the error and look like it's an object. calling .replace on error doesn't make sense

here is my error

{
  file: 'src/integration/00010-login/login.spec.ts:9:10',
  message: "\x1B[90mTS2339: \x1B[39mProperty 'waitForLoadingModalClose' does not exist on type 'cy & EventEmitter'.\r\n" +
    '  \x1B[0m \x1B[90m  7 |\x1B[39m     beforeEach(\x1B[36mfunction\x1B[39m () {\x1B[0m\r\n' +
    "  \x1B[0m \x1B[90m  8 |\x1B[39m       cy\x1B[33m.\x1B[39mvisit(\x1B[32m'auth/login'\x1B[39m)\x1B[33m;\x1B[39m\x1B[0m\r\n" +
    '  \x1B[0m\x1B[31m\x1B[1m>\x1B[22m\x1B[39m\x1B[90m  9 |\x1B[39m       cy\x1B[33m.\x1B[39mwaitForLoadingModalClose()\x1B[33m;\x1B[39m\x1B[0m\r\n' +
    '  \x1B[0m \x1B[90m    |\x1B[39m          \x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[0m\r\n' +
    '  \x1B[0m \x1B[90m 10 |\x1B[39m       \x1B[90m// to solve some login page test failures due to incomplete page load\x1B[39m\x1B[0m\r\n' +
    `  \x1B[0m \x1B[90m 11 |\x1B[39m       cy\x1B[33m.\x1B[39m\x1B[36mget\x1B[39m(\x1B[32m'button span:contains("Login")'\x1B[39m\x1B[33m,\x1B[39m { timeout\x1B[33m:\x1B[39m \x1B[35m60000\x1B[39m })\x1B[33m.\x1B[39mshould(\x1B[32m'be.visible'\x1B[39m)\x1B[33m;\x1B[39m\x1B[0m\r\n` +
    '  \x1B[0m \x1B[90m 12 |\x1B[39m     })\x1B[33m;\x1B[39m\x1B[0m',
  details: undefined,
  stack: "Error: \x1B[90mTS2339: \x1B[39mProperty 'waitForLoadingModalClose' does not exist on type 'cy & EventEmitter'.\r\n" +
    '  \x1B[0m \x1B[90m  7 |\x1B[39m     beforeEach(\x1B[36mfunction\x1B[39m () {\x1B[0m\r\n' +
    "  \x1B[0m \x1B[90m  8 |\x1B[39m       cy\x1B[33m.\x1B[39mvisit(\x1B[32m'auth/login'\x1B[39m)\x1B[33m;\x1B[39m\x1B[0m\r\n" +
    '  \x1B[0m\x1B[31m\x1B[1m>\x1B[22m\x1B[39m\x1B[90m  9 |\x1B[39m       cy\x1B[33m.\x1B[39mwaitForLoadingModalClose()\x1B[33m;\x1B[39m\x1B[0m\r\n' +
    '  \x1B[0m \x1B[90m    |\x1B[39m          \x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[0m\r\n' +
    '  \x1B[0m \x1B[90m 10 |\x1B[39m       \x1B[90m// to solve some login page test failures due to incomplete page load\x1B[39m\x1B[0m\r\n' +
    `  \x1B[0m \x1B[90m 11 |\x1B[39m       cy\x1B[33m.\x1B[39m\x1B[36mget\x1B[39m(\x1B[32m'button span:contains("Login")'\x1B[39m\x1B[33m,\x1B[39m { timeout\x1B[33m:\x1B[39m \x1B[35m60000\x1B[39m })\x1B[33m.\x1B[39mshould(\x1B[32m'be.visible'\x1B[39m)\x1B[33m;\x1B[39m\x1B[0m\r\n` +
    '  \x1B[0m \x1B[90m 12 |\x1B[39m     })\x1B[33m;\x1B[39m\x1B[0m\n' +
    '    at C:\\repo\\PPMS2\\frontend-temp\\node_modules\\fork-ts-checker-webpack-plugin\\lib\\hooks\\tapAfterCompileToGetIssues.js:38:27\n' +
    '    at Array.forEach (<anonymous>)\n' +
    '    at Object.<anonymous> (C:\\repo\\PPMS2\\frontend-temp\\node_modules\\fork-ts-checker-webpack-plugin\\lib\\hooks\\tapAfterCompileToGetIssues.js:37:16)\n' +       
    '    at Generator.next (<anonymous>)\n' +
    '    at fulfilled (C:\\repo\\PPMS2\\frontend-temp\\node_modules\\fork-ts-checker-webpack-plugin\\lib\\hooks\\tapAfterCompileToGetIssues.js:5:58)\n' +
    '    at processTicksAndRejections (internal/process/task_queues.js:93:5)'
}

it's a ts error as it can't find the definition for the waitForLoadingModalClose, a solution for that would be to add the definition into th support folder

@mhamri
Copy link

mhamri commented Sep 7, 2021

for god sake fix it, it's as easy as this, this error is there since version 4

function cleanseError (err) {
  if (typeof err!=="string"){
    err= Object.values(err).join('\n\n');
  }

  return err.replace(/\n\s*at.*/g, '').replace(/From previous event:\n?/g, '');
}

and it will shows the error correctly

image

@pavankjadda
Copy link

Cypress webpack-preprocessor does not yet support Webpack 5 as explained in this issue: #8900

We released a temporary version of this package that supports webpack v5 – npmjs.com/package/cypress-webpack-preprocessor-v5

npm i cypress-webpack-preprocessor-v5

Is anyone getting this error outside of using Webpack 5? Because we will close this issue if not as it's a duplicate of #8900

This still does not fix the issue.

@rkrisztian
Copy link

rkrisztian commented Oct 4, 2021

While we're waiting for a fix, we can use patch-package with @mhamri's code line changes, to alleviate the problem a bit (just in case you didn't know).

Edit: I am too late with this, due to more recent releases of @cypress/webpack-preprocessor.

@mhamri
Copy link

mhamri commented Oct 5, 2021

@rkrisztian my code is already part of the package, even the double \n 🤣

@amitasil
Copy link

Getting issue with Cypress 9.0 now, with a new installation

@stavares843
Copy link

same, any ETA?

@mayurrawte
Copy link

Any updates on this ?

@stavares843
Copy link

using nvm install 16.13.0 fixed the issue

seems was an issue with using node 17

@andrei-dascalu
Copy link

I am also getting this with node 17

@JimLynchCodes
Copy link

Cypress seems to be still broken on node v17. None of the above solutions worked for me so I just downgraded npm... 🤷‍♂️

@emilyrohrbough
Copy link
Member

emilyrohrbough commented Jan 25, 2022

@JimLynchCodes are you having this issue with cypress >= 7.7.0? Can you confirm you are using the latest version of @cypress/webpack-preprocessor version 5.11.0?
cypress/webpack-preprocessor version 5.9.1+ should handle the scenario when the error is not a string and was pulled into Cypress 7.7.0.

benjaminEwhite pushed a commit to newsrevenuehub/rev-engine that referenced this issue May 24, 2022
Started getting a cryptic `TypeError: err.replace is not a function`
error when trying to run cypress tests locally.

As per suggestion in this GH comment, upgraded and solved problem:

cypress-io/cypress#8948 (comment)
benjaminEwhite pushed a commit to newsrevenuehub/rev-engine that referenced this issue Jul 22, 2022
Started getting a cryptic `TypeError: err.replace is not a function`
error when trying to run cypress tests locally.

As per suggestion in this GH comment, upgraded and solved problem:

cypress-io/cypress#8948 (comment)
@nagash77 nagash77 added the prevent-stale mark an issue so it is ignored by stale[bot] label Apr 3, 2023
@jennifer-shehane
Copy link
Member

Closing as resolved.

If you're experiencing a bug similar to this in Cypress, please open a new issue with a fully reproducible example that we can run. There may be a specific edge case with the issue that we need more detail to fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
prevent-stale mark an issue so it is ignored by stale[bot] stage: awaiting response Potential fix was proposed; awaiting response topic: preprocessors 🔧 type: bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.