Pete Nykänen

One option would be taking the repository field as a last resort and checking if `.npmignore` exists in the repo. Maybe behind a `--i-just-want-to-be-really-really-sure` flag or something :ok_hand:

Thanks for the prompt reply! The use case here is quite limited, but if I get around to implement it myself, I'll shoot you with a PR :)

Thanks @rprouse, in my case I had used a wrong environment variable for username and the error didn't exactly lead to the correct place :) I think the error message...

Using `options[]` with `element.selectedIndex` works great, so the sizing issue is fixed :+1: However, `cs[appearance]` is undefined on IE11 in [stretchy.js#L105](https://github.com/LeaVerou/stretchy/blob/gh-pages/stretchy.js#L105), which is why it doesn't account for the 2em...

It is, at least on IE11 Mobile :+1:

As far as I understand, setting the runtime parameter to Runtime.NODEJS20_X does exactly that, it sets the IMAGE ARG to sam/build-nodejs18.x. I am not familiar enough with the internals of...

The issue went away after updating to MacOS Sonoma 14.2.1, which seem to point similar kinds of OpenSSL issues as with https://github.com/aws/aws-sam-build-images/issues/116 but I don't think one can pass build...

Fix for the actual issue is tracking in https://github.com/postgis/docker-postgis/pull/395/files

Thanks @sebastic and @ImreSamu for clarifications, in our use-case we are tied to a platform provider (eg. Google Cloud SQL, Postgres for Azure) and we want to run our CI...

I'd happily not pin any versions anywhere, but as said we are often constricted by our platform providers and there's always a risk of doing something incompatible when doing so....