Closed da-kami closed 4 years ago
:( actually does not build & bundle properly like this. The comit-sdk
install has to be triggered separately.
:( actually does not build & bundle properly like this. The
comit-sdk
install has to be triggered separately.
Do you mean the yarn build
command? Or the CI?
Would adding a second app
yarn install
for the comit-sdk
work in the Github Actions worfklow?
To enable proper hot-swapping, I think we'd need to port the code to the app directly (importing the files and dependencies into the taker-ui
project itself) instead of as a file module.
To enable proper hot-swapping, I think we'd need to port the code to the app directly (importing the files and dependencies into the
taker-ui
project itself) instead of as a file module.
Yep, that is what I suggested as well. I think @da-kami is now taking this approach :)
Closing this for now, will re-open once sorted out.
Keep the SDK within the app until it is finished and then decide what to upstream. The
app
links thecomit-sdk
using thefile:
handle in thepackage.json
.Note: Initially pulled the SDK into the
app
folder, but when runningyarn install
in the project root (taker-ui
folder) thecomit-sdk
was not properly installed insideapp
. By pulling it one level up (outsideapp
) the installation of the dependencies work, however, changes on thecomit-sdk
are not hot-swapped into theapp
. (Which is annoying because runningyarn install
in theapp
folder is very time consuming). Note that initially I tried to pull the SDK code in without using it as a module (just link to the app-code directly and remove dependency from app'spackage.json
), but that caused packaging errors that I could not easily resolve.@thomaseizinger @bonomat if you have a better strategy for this once you see it please ping me. No need to invest too much brainpower though :)