Burak Yigit Kaya

I would assume the code to live here at the beginning until it is more broadly adopted (may move into its own repo or under getsentry/sentry).

@chadwhitacre quite sure this is related to getsentry/sentry#31615 which changed the option store model. @markstory pointed out that these options are very different from the options being refactored this line...

I certainly read the newsletter, that said you know where to find me anyways 😅

@darklow would you be interested in submitting a PR to get this right?

@chadwhitacre I guess we can build the cron images periodically ourselves?

>Why do we currently build on install vs. build-once? It has to do with configuration, I think? Not really the configuration at the moment. We had this for Sentry image...

Another idea (from @davidaurelio): Put publish behind a company SSO so all company projects are published by the same, single user account on NPM).

Have any of you tried using `--prefer-offline` or `--offline`? That should work IMO.

The thing is, we still need those `package.json` files to have a consistent image of the resolved file tree, even if those dependencies won't be installed. An alternative would be...

Which version of Yarn are you using?