Closed AndyTitu closed 7 months ago
With this project being split up into multiple packages (client
, examples
) I would probably expect that we should set up workspaces. This is common for repos containing multiple packages, so projects can effectively cross-link dependencies, and so that someone working in the repo can perform actions (like installing dependencies, building, testing, etc) from the top-level directory. Check our workspaces for npm.
With this project being split up into multiple packages (client, examples) I would probably expect that we should set up workspaces. This is common for repos containing multiple packages, so projects can effectively cross-link dependencies, and so that someone working in the repo can perform actions (like installing dependencies, building, testing, etc) from the top-level directory. Check our workspaces for npm.
Added the workspaces! Modified the "how to test" section to more easily run the project
Did a user test and it works well. It does not call into the actual sdk-core or error just yet, but it seems to be calling the correct functions.
✅
Manually tested the finalizer and it seems to be called correctly.
Manually tested again, still works. But now I get an IDE error on the finalization registry:
Cannot find name 'FinalizationRegistry'.
Manually tested again, still works. But now I get an IDE error on the finalization registry:
Cannot find name 'FinalizationRegistry'.
This is odd. Have you tried restarting the typescript service, or just recompiling? That fixed it for me last time I encountered that.
This PR refactors the code and refines a few configurations:
from "./core"
tofrom "./core.js"
How to test
npm install
npm test
npm run esm-example
npm run commonjs-example