chris (fool) mccraw

Not certain you'd call this a bug - tis probably operating as designed - but, I think, not as intended and not as customers desire :)

@defce74 looks like you've tried to set a version of 'python-3.7'. That'll lead to failure like the one you describe. Use `3.7` instead and i bet your build works.

related issue: https://github.com/netlify/build-image/issues/296

thinking out loud: we could also fork that travis script, change it, and use our own copy, non?

Indeed. But in a monorepo, you cannot set base if you want to build two or more separate code bases. I am aware it is a heavy lift and that's...

How does that help this use case? my repo has 2 subprojects. Both have individual package.json files. There is no /package.json. My build command is this: ``` cd project1 &&...

We think this is affecting yarn too in monorepos, and are doing some tests to confirm. Reported in customer cases: - https://app.intercom.io/a/apps/q245f50x/inbox/inbox/unassigned/conversations/18572475790 - https://app.intercom.io/a/apps/q245f50x/inbox/inbox/unassigned/conversations/18991508943

As far as I know, our builds should support every released version of node and yarn. It is the specific inclusion of the `engines` line that may be problematic, or...

thanks for the ping @micleners ! Any updates to this functionality will be posted in this thread :) None are planned today as far as I know. The workarounds listed...

that's not true, @noisy . You can use any node version you want; you need to set a node version in our way, which is use `$NODE_VERSION` and put whatever...