WARNING: Replace fill-available to stretch, because spec had been changed

[JaxonWright]

Expected behavior.

Not have warnings like this when building node dependency with a project.

Actual behavior.

Steps to reproduce the problem.

Build a project that has this project as one of its npm dependencies

Editor version.

3.1.1

OS.

Windows 10 1909

Browser.

Irrelevant

[flonussi]

This exact issue appeared today for me also.
But I'm stil on 3.1 and didn't touch or update froala or any other dependency of my project in weeks, but today this warning started to appear...
In addition to that issue I also get a warning about a crypto module, but as I already said, I didn't touch anything

[jvmills]

Same for me

`WARNING in ./node_modules/froala-editor/css/froala_editor.pkgd.min.css (./node_modules/css-loader??ref--5-2!./node_modules/postcss-loader/src??postcss0!./node_modules/froala-editor/css/froala_editor.pkgd.min.css)
Module Warning (from ./node_modules/postcss-loader/src/index.js):
Warning

(7:52021) Replace fill-available to stretch, because spec had been changed
@ ./resources/sass/app.scss (./node_modules/css-loader??ref--5-2!./node_modules/postcss-loader/src??postcss0!./node_modules/sass-loader/dist/cjs.js??ref--5-4!./resources/sass/app.scss) 9:10-173
@ ./resources/sass/app.scss`

[marctaule]

Same for me...

[wes337]

Same, can this please get fixed?

[qingmang]

Same for me...

[arwinvdv]

I had contact with Froala today and they will fix the issue in v3.2.4 what will be released in a few months.

[devstack-be]

@arwinvdv Thanks for the information ;)

[micheleh]

Is there a way to work around this until a fix is provided?

[devstack-be]

normally npm is not blocking the script. it's just a warning. If you want to fix it, you can explore the package, do a search and replace and replace "fill-available" to "stretch". But it's only temporary and it's better waiting a real fix.

[paras-deshbhratar]

Even I am also getting the same warning in console.
Thanks @arwinvdv. Will wait till they release v3.2.4

[marcodeluca]

Thanks for the update, having the same issue.

[marting169]

gracias!

[manshu]

I've the same issue. Any update on this?

[ffjanhoeck]

Same issue :)