Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Field doesn't contain a valid alias configuration error on docker build #16119

Closed
AyoubGhaddab opened this issue Jan 11, 2021 · 3 comments · Fixed by #16192
Closed

Field doesn't contain a valid alias configuration error on docker build #16119

AyoubGhaddab opened this issue Jan 11, 2021 · 3 comments · Fixed by #16192
Assignees
Labels
A-Packaging Packaging, signing, releasing P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect

Comments

@AyoubGhaddab
Copy link

Description

Hello, i wanted to install Element develop branch using docker; I have foloowed the steps mentioned in github:
sudo docker build -t chat

--build-arg USE_CUSTOM_SDKS=true

--build-arg REACT_SDK_REPO="https://github.com/matrix-org/matrix-react-sdk.git"

--build-arg REACT_SDK_BRANCH="develop"

--build-arg JS_SDK_REPO="https://github.com/matrix-org/matrix-js-sdk.git"

--build-arg JS_SDK_BRANCH="develop"

.
during the yarn install step, i have got this error:
using description file: /src/react-sdk/package.json (relative path: ./src)
Field 'matrix_src_browser' doesn't contain a valid alias configuration
Field 'browser' doesn't contain a valid alias configuration
using description file: /src/react-sdk/package.json (relative path: ./src/component-index)
no extension

how can I solve this ? thank you

Steps to reproduce

  • run docker build -t chat in Element web project

Version information

  • Platform: web (in-browser)

For the web app:

  • OS: Ubuntu
@kkorniszuk
Copy link

Did you find any solution?

@jryans jryans added A-Packaging Packaging, signing, releasing P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround defect labels Jan 15, 2021
@jryans jryans self-assigned this Jan 15, 2021
@jryans
Copy link
Collaborator

jryans commented Jan 15, 2021

Thanks for the report, I can see that Docker Hub builds of develop are also failing, likely in a similar way. (Though release builds are working.) I'll take a look soon, hopefully on Monday.

jryans added a commit that referenced this issue Jan 18, 2021
An extra step is needed for develop Docker builds after recent build process
changes. This was regressed by
#15999.

Fixes #16119
@jryans
Copy link
Collaborator

jryans commented Jan 18, 2021

Docker Hub develop builds are working again, so I assume this also fixes the issue for reporters here as well, but do let us know if there's further trouble.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Packaging Packaging, signing, releasing P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants