There have been a few issues with setting up frontend that I’ve managed to resolve.
git clone command doesn’t work, use the format in core setup doc works fine.
then script /setup gives this error:
Command ‘yarn’ not found, but can be installed with:
sudo apt install cmdtest
Doing what it suggest leads to more misery.
Instead, install Yarn manually:
curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
echo “deb https://dl.yarnpkg.com/debian/ stable main” | sudo tee /etc/apt/sources.list.d/yarn.list
sudo apt-get update
sudo apt-get install yarn -y
yarn install
Above mentioned in case it’s relevant to what follows:
script/setup
➤ YN0000: · Yarn 4.3.1
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed in 0s 296ms
➤ YN0000: ┌ Post-resolution validation
➤ YN0060: │ #typescript-eslint/eslint-plugin is listed by your project with version 7.17.0 (p74769), which doesn’t satisfy what eslint-config-airbnb-typescript and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ eslint is listed by your project with version 8.57.0 (pf1360), which doesn’t satisfy what #typescript-eslint/eslint-plugin and other dependencies request (but they have non-overlapping ranges!).
➤ YN0002: │ home-assistant-frontend#workspace:. doesn’t provide #octokit/core (pafdb1), requested by #octokit/plugin-retry.
➤ YN0002: │ home-assistant-frontend#workspace:. doesn’t provide browserslist (p7eeaf), requested by browserslist-useragent-regexp.
➤ YN0002: │ home-assistant-frontend#workspace:. doesn’t provide component-emitter (p20f8d), requested by vis-network.
➤ YN0002: │ home-assistant-frontend#workspace:. doesn’t provide keycharm (p74fdd), requested by vis-network.
➤ YN0002: │ home-assistant-frontend#workspace:. doesn’t provide uuid (pf0b74), requested by vis-data and other dependencies.
➤ YN0002: │ home-assistant-frontend#workspace:. doesn’t provide vis-util (p6a7fd), requested by vis-data and other dependencies.
➤ YN0086: │ Some peer dependencies are incorrectly met by your project; run yarn explain peer-requirements for details, where is the six-letter p-prefixed code.
➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed in 0s 993ms
➤ YN0000: ┌ Link step
➤ YN0007: │ normalize-diacritics#npm:2.14.0 must be built because it never has been before or the last one failed
➤ YN0007: │ #reallyland/esm#npm:0.0.1 must be built because it never has been before or the last one failed
➤ YN0007: │ lit-ntml#npm:2.20.0 must be built because it never has been before or the last one failed
➤ YN0007: │ nodemod#npm:2.8.4 must be built because it never has been before or the last one failed
➤ YN0007: │ app-datepicker#npm:5.1.1 must be built because it never has been before or the last one failed
➤ YN0000: └ Completed in 1m 41s
➤ YN0000: · Done with warnings in 1m 42s
/mnt/b/HomeAssistant/frontend$ yarn explain peer-requirements p74769
Package home-assistant-frontend#workspace:. is requested to provide #typescript-eslint/eslint-plugin by its descendants
home-assistant-frontend#workspace:.
├─ eslint-config-airbnb-typescript#npm:18.0.0 [4fe94] (via ^7.0.0)
└─ eslint-plugin-unused-imports#npm:4.0.1 [4fe94] (via ^8.0.0-0)
✘ Package home-assistant-frontend#workspace:. provides #typescript-eslint/eslint-plugin with version 7.17.0, which does not satisfy all requests.
Unfortunately, the requested ranges have no overlap
Do I need to hack the script to require compatible version numbers?
Or will that just mess up other stuff by doing so?
What’s the right approach to resolve this?
Cheers.