Comments (13)
jquense
commented on June 15, 2024
1
I am not sure why --ignore-optional doesn't work in some cases, but it doesn't seem safe as a default. Clearing that, fixed the problem.
As an aside I do think better defaults for YARN_FLAGS should include --pure-lockfile or --frozen-lockfile Yarn recommends --frozen-lockfile for CI builds but it's a bit opinionated
from build-image.
brycekahle
commented on June 15, 2024
1
Yarn finally updated in #130. I'll close this issue when the new image has been deployed.
from build-image.
fool
commented on June 15, 2024
for our troubleshooting: similar report from another customer: https://app.intercom.io/a/apps/q245f50x/respond/inbox/1479299/conversations/12192293322
from build-image.
fool
commented on June 15, 2024
Netlify Support todo:
- get a simpler reproduction case by:
- create a site using workspaces with 1 dependency
- add a second dependency in a subdir/package.json and confirm fail
- build with a cleared cache and confirm success
- update this bug (remove needs-review, update title + repro case)
from build-image.
fool
commented on June 15, 2024
We were unable to get a simpler example that we could try debugging to fail, @Aleksion - if you come up with a repro case that is less involved, let us know and we'll reopen this.
from build-image.
Aleksion
commented on June 15, 2024
Sounds good. I'll dive into it the next time I hit it!
from build-image.
jquense
commented on June 15, 2024
arg this is a really magical bug :/ I can't manage to put a simpler repro together but this fails consistently on every gatsby netlify deploy when we try with workspaces. Myself and @KyleAMathews independently confirm it does not occur running the docker image locally, or in any other context except for an actual deploy. We've tried changing the versions of node and yarn to no effect and i see no information about this error anywhere:
https://app.netlify.com/sites/using-wordpress/deploys/59f8d06ddf995350b4b3712a
from build-image.
fool
commented on June 15, 2024
when you run the docker image locally, do you follow the steps to run with
cache just about the 'Contributing' section in README.md? If not - and if
you don't also set all your environment variables like this:
```
test-tools/test-build.sh path/to/your/repo 'export VAR1=value ; export
VAR2=value2 ; your build command'
```
(and then run it again with the `export T=tmp/tmp.XXXXX` in there as well
to get the cache setup)
…On Tue, Oct 31, 2017 at 12:43 PM, Jason Quense ***@***.***> wrote:
arg this is a really magical bug :/ I can't manage to put a simpler repro
together but this fails consistency on every gatsby netlify deploy when we
try with workspaces. Myself and @KyleAMathews
<https://github.com/kyleamathews> independently confirm it does not occur
running the docker image locally, or in any other context *except* for an
actual deploy. We've tried changing the versions of node and yarn to no
effect and i see no information about this error anywhere:
https://app.netlify.com/sites/using-wordpress/deploys/
59f8d06ddf995350b4b3712a
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#89 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAN-oHhE0hyvZkg5b6ZBzkhKNQQNSXf7ks5sx3hjgaJpZM4PzEti>
.
from build-image.
jquense
commented on June 15, 2024
As is usually the case, just after posting I figures it out. The problem is that the default YARN_FLAGS ignores optional deps which for some reason doesn't play nice with workspaces with some packages with post install scripts. Still not sure why I can't reproduce the issue with docker locally tho
from build-image.
fool
commented on June 15, 2024
so - what YARN_FLAGS do work? We'll want to write some documentation
around that once we understand your solution :)
…On Tue, Oct 31, 2017 at 6:20 PM, Jason Quense ***@***.***> wrote:
As is usually the case, just after posting I figures it out. The problem
is that the default YARN_FLAGS ignores optional deps which for some reason
doesn't play nice with workspaces with some packages with post install
scripts. Still not sure why I can't reproduce the issue with docker locally
tho
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#89 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAN-oFXSUJLA8wsBlg_dSPlbf-NltiGBks5sx8dBgaJpZM4PzEti>
.
from build-image.
oskarrough
commented on June 15, 2024
Can confirm that setting YARN_FLAGS='--no-ignore-optional solves it.
I get the error when YARN_VERSION is set and node-sass is used. I assume it's something with node-sass's postinstall hook + optional dependencies?
Can we change the defaults ala what @jquense suggests and maybe finally update the default Yarn version as well? :) #122
from build-image.
Bouncey
commented on June 15, 2024
I'm guessing the new image was deployed within the last 24 hours? Our CSS just broke on a gatsby site
from build-image.
brycekahle
commented on June 15, 2024
Yes, my apologies. We deployed yesterday afternoon. @Bouncey if you reach out to support, they can help solve your problem.
from build-image.
Related Issues (20)
- Customizable Java version HOT 2
- Latest NPM versions throw an error when workspaces are configured HOT 1
- Missing workdir "/opt/build" in build container.
- Change the way how the elm compiler is installed as it is not compatible with arm64 HOT 2
- Why is the Hugo version out of date so much?
- Add Haldo linting to build image dockerfile HOT 1
- Run the docker image size inside CircleCI instead of github actions
- Container-structure-tests fail for arm64 HOT 2
- Create multiarch images and push them to the dockerhub HOT 5
- Cache Playwright browser dependencies HOT 3
- `target` directory for Rust is not stored
- Local build test fails with podman HOT 1
- Builds fail when using `[email protected]` HOT 5
- Same codebase stopped compiling in version 4.13 HOT 4
- Monorepo project cannot found pnpm HOT 2
- Failed to debug netlify locally HOT 1
- Add Support for .NET 7 HOT 6
- `NETLIFY_USE_PNPM: true` environment var not working after v4.15.0 HOT 1
- Show an understandable error when `getBuildInfo` failed
- Not respecting pnpm version specified in packageManager field of package.json HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from build-image.