Dan Tonon

I think a new `strict` setting would be good. ```js // same as grid: true but only allows Grid if grid-areas is used autoprefixer({grid: true, strict: "grid"}) // same as...

> Why not grid: strict? Because I was over thinking it 😅 If we do go with `{grid:"strict"}` we should also provide `{grid:"strict-autoplace"}` so that people on old projects that...

Ok so to clear things up: ``` // grid: on in strict mode {grid:"strict"} // grid: "autoplace" in strict mode {grid:"strict-autoplace"} // grid: on in strict mode /* autoprefixer grid:...

The issue that @fabb has is that he is working on a project that is old and not autoplacement compatible. If we make `strict` mode only available when autoplacement is...

If we go down the path of insentivising devs to upgrade their code bases, then these would be the new changes needed: ``` // grid: "autoplace" in strict mode {grid:"strict"}...

> Actually my project is not so old 😅 It currently exists, thus it's old 😜

The point of strict mode is to force people to use either the autoplacement algorithm or grid areas. If autoplacement is causing an issue then that means that you should...

Or are you saying that this should equate to `grid: on`? ``` /* autoprefixer grid: non-strict */ ``` Actually maybe that is better. If the user is turning off strict...

@bogdan0083 could you take a look at this issue? I would like to be able to mention this feature in my upcoming autoplacement article but it needs to be implemented...

@fabb If someone has Autoprefixer running twice that is a problem with their config, not with Autoprefixer. Your use case is not Autoprefixer's concern. @bogdan0083 That’s fine. It's the holiday...