Follow up question, running locally, and having the frontend interact.
Currently with 3 separate dars, I pass the dars into the codgen js script, this ultimately generates my daml.js in the ui directory, upon which when I do npm install, it installs the types.
and in my package.json, I am importing the new js types. Now this is for deploying on daml hub.
To do this locally, you mentioned I create a dummy project.
In order to run daml start, I need to do daml build. So are you saying that create a new directory, I’ll call it localBuild
and in there, I’ll have a daml.yaml that imports the deps, eg
# for config file options, refer to
# https://docs.daml.com/tools/assistant.html#project-config-file-daml-yaml
sdk-version: 1.18.1
name: LocalBuild
source: daml
version: 0.0.1
dependencies:
- ../Asset/asset.dar
- ../User/user.dar
- ../Account/account.dar
sandbox-options:
- --wall-clock-time
- --ledgerid=wallet-refapp-sandbox
When I do daml build, that creates a new .daml file, with new dependency packages. These packages need to be installed in the frontend, but that means the js types are all different. Meaning I need to have a whole other set of imported JS types for a local build, and a build for daml hub? Or am I missing something, it seems kind of awkward.