ehmicky

Results 372 comments of ehmicky

Hi @Tom-Bonnike, I just reported this bug to the team working on the CSS post-processing. We will let you know as soon as this is fixed!

Unfortunately not. The team responsible of this is aware of this bug. They mentioned also several other bugs related to HTML tags being messed up during CSS post-processing. Tagging them...

This looks all good :+1: with the two following suggestions. I think the `multiple` property and the `repeat` property could be merged into one. For example, if `type: select` and...

What I meant about `multiple` and `repeat`: `repeat` would have the generic meaning you're describing above. But when used inside a select field, it would have the additional meaning of...

The removal was backported to Next 9 users in https://github.com/netlify/netlify-plugin-nextjs/pull/159 I am hoping this will decrease the percentage of users still using the legacy directory ([Humio query](https://cloud.us.humio.com/netlify-us-production/search?query=%22netlify-automatic-functions%22&live=false&start=7d&fullscreen=false)).

Thanks for reporting this @mraerino. The underlying problem is described at https://github.com/netlify/build/issues/1255 Also, https://github.com/netlify/pod-the-builder/issues/68 is related

Hi @bahmutov, At the moment, we are using the `SITE` environment variable. Our current plugins allow usually allow users to override it with `plugin.config.site` (see [example](https://github.com/netlify/build/blob/master/packages/netlify-plugin-axe/index.js#L11)). @DavidWells Could you confirm...

I think the `SITE` environment variable is setup by our BuildBot alongside [other environment variables](https://www.netlify.com/docs/continuous-deployment/#environment-variables) which might help you as well. The BuildBot is the environment in which `netlify/build` is...

We have a pending PR at #513 to add the base support for this. Once this is merged, we will need to do some additional work in this repository to...

@mwickett We are still on the design phase for this feature. It turns out it requires some rather big infrastructure changes so we are evaluating the best way to approach...