I've found some limitations on the dnt and other deno to node converters (s.a., deno2node). They are non-blocking limitations but it's worth posting notes on them:
These converters don't recognize very well any import mapping configured in the project.
Bundling the deno project first solves 1., however deno bundles don't support typing yet (it's an open issue), so the npm node packages won't be very well typed. This is unfortunate specially for the Plugins framework, because types make it easier for the community to build compatible Plugins.
The FSML SDK code is written in Deno, however the plan is to also release the SDK for Node.
There's the dnt package which is a Deno to Node converted recommended by the Deno official documentation