Element-web: apparently `npm i && npm start` doesn't work on develop or experimental atm
we need to CI these surely, and remember to repoint the deps in package.json or whatever is going wrong
ara4n
All 5 comments
Do you mean it doesn't work after following the dev environment setup instructions?
How does the build happen for CI?
lampholder
on 2 Jan 2019
It worked for me building /develop this morning
lampholder
on 3 Jan 2019
this was @martindale complaining of build errors when trying to run npm i && npm start on a develop checkout of riot-web. The theory is that the dep on matrix-react-sdk hadn't been unpinned to develop, so it was trying to use the wrong matrix-react-sdk. Dunno if someone fixed it since or if something else was wrong.
the discussion subsequently slid into a "why is the majority of the app in a library" discussion.
ara4n
on 3 Jan 2019
I believe #7728 describes a potential way to fix the cause of this.
jryans
on 3 Jan 2019
We now set the deps back to develop after release, so I believe this should be fixed now.
jryans
on 2 Jan 2020
Related issues
n-o-o-b
路
3Comments
NotAFile
路
3Comments
PureTryOut
路
3Comments
niedzielski
路
3Comments
ara4n
路
3Comments
Most helpful comment
this was @martindale complaining of build errors when trying to run
npm i && npm starton a develop checkout of riot-web. The theory is that the dep on matrix-react-sdk hadn't been unpinned to develop, so it was trying to use the wrong matrix-react-sdk. Dunno if someone fixed it since or if something else was wrong.the discussion subsequently slid into a "why is the majority of the app in a library" discussion.