fix(web): resolved web build issues with yarn and missing dependencies #1658
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I had trouble building the web UI on my local machine. I resolve them via dependency changes and changing the package manager to
yarn
. Usingyarn
leads to faster install/build times and more general intelligence around managing dependencies, so I recommend we switch over. However, my main goal for this change is to establish a repeatable build process for the web UI.Machine Information
Issues
package-lock.json
withnpm i
resulted in an install failure due to a missingmetadata.js
dependency. I found this StackOverflow post, whose answer involved directly specifyingmonaco-editor
as a dependency. I added that and then faced several failed dependency errors. I then triedyarn install
and the install worked.How Has This Been Tested?
Steps to Reproduce
Steps to Verify
Snapshots:
Install Fail on Alibaba Registry
Install Fail on Fresh npm Install
Success with Yarn
Checklist: