mirror of
https://github.com/digital-asset/daml.git
synced 2024-09-21 09:48:35 +03:00
ba27ea9af4
Our plan for `daml2js` is to populate the `name` and `version` field of the generated `package.json` files with the name and version of the input DALF. Once this is done, you would expect to refer to the package generated from `create-daml-app-0.1.0.dar` via ```typescript import ... from '@daml.js/create-daml-app';` ``` Since we currently depend on the package by file paths anyway, we can already pretend to have the right behavior in place. In this style you can also depend on two different versions of the same DAML package. This will happen during upgrades, a situation we're already facing in DAVL. There it can be solved via the following two lines in the `dependencies` field of the `package.json`: ``` ... "davl-v4": "file:../daml.js/davl-0.0.4", "davl-v5": "file:../daml.js/davl-0.0.5", ... ``` CHANGELOG_BEGIN CHANGELOG_END |
||
---|---|---|
.. | ||
index.test.ts |