microsoft / microsoft/node-api-dotnet
Multiple NodeJsEnvironments
@vmoroz is already working on this.
Since Mar 14, 2025.
- Dominant language
- C#
- Stars
- 783
- Forks
- 80
- PR merge metrics
- No merged PRs in 30d
Description
We had a project that was performing interop from .NET to JS using version 0.8.20 but were getting a couple of intermittent errors when trying to run outside of our development environment.
The two errors we are getting are:
- Already initialized. The
initializefunction can be used only once. - The JS reference cannot be accessed from the current thread.
We tried to resolve this by updating to the latest nuget packages but it looks like there have been some breaking changes and the docs are no longer up-to-date.
We are using DI and used to store NodeJsPlatform as a singleton and register NodeJsEnvironment as scoped and pass this into another scoped service that executes some JavaScript to render a PDF report.
We have now replaced this with NodeEmbeddingPlatform as a singleton which is passed into the scoped report generation service which then creates a NodeEmbeddingThreadRuntime via platform.CreateThreadRuntime(); and executes await threadRuntime.Run(async () =>...
With the latest code when trying to create the NodeEmbeddingPlatform we get the following error:
"System.EntryPointNotFoundException : Unable to find an entry point named 'node_embedding_platform_create' in DLL."
Could someone please give us some hints as to how to get the latest version working and any pointers as to what our initial issues may be related to?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.