You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran into an issue with the yarn build platform --linux command when building Docker images. The latest version switched from node-sass to dart-sass, and when compiling for a specific OS, the build can fail without a clear error message—just an exception from the dart-sass-embeddable module.
After some digging, I found that dart-sass-embeddable requires the glibc compiler, but not all Linux distributions support it. In our case, we were using Alpine Linux, which relies on musl instead of glibc, leading to compatibility issues.
While the transition from node-sass to dart-sass is documented, there’s no mention of potential issues when using a distribution that doesn't support glibc. I’m opening this issue to suggest updating the Developer Guide to explicitly state that when building the platform, developers should use a distribution compatible with glibc.
This happened inside a Docker environment, but I’m assuming it could also occur outside of a containerized setup. Would love to get this clarified in the docs.
Thanks!
The text was updated successfully, but these errors were encountered:
Hey,
I ran into an issue with the
yarn build platform --linux
command when building Docker images. The latest version switched from node-sass to dart-sass, and when compiling for a specific OS, the build can fail without a clear error message—just an exception from the dart-sass-embeddable module.After some digging, I found that dart-sass-embeddable requires the glibc compiler, but not all Linux distributions support it. In our case, we were using Alpine Linux, which relies on musl instead of glibc, leading to compatibility issues.
While the transition from node-sass to dart-sass is documented, there’s no mention of potential issues when using a distribution that doesn't support glibc. I’m opening this issue to suggest updating the Developer Guide to explicitly state that when building the platform, developers should use a distribution compatible with glibc.
This happened inside a Docker environment, but I’m assuming it could also occur outside of a containerized setup. Would love to get this clarified in the docs.
Thanks!
The text was updated successfully, but these errors were encountered: