staytuned_team
How to create private packages in deno and not fall into ERR_UNSUPPORTED_NODE_MODULES_TYPE_STRIPPING
facing similar issue when we tried to publish a deno package to github private npm registry and use it in deno. have you found any solution for such problem?
3 replies
Resolving Dependencies for Local ESM NPM Packages in Deno
The Problem:
With the above configuration, how can I configure the Deno app so that it does not need any imports for
uuid, marked, or lodash? All I want to do is for it to import package2 but have all of its dependencies pulled and loaded as well. How can I make Deno automatically detect and resolve the dependencies of my local NPM package without me having to manually specify them in the deno.json?
Steps Taken:
1. Ensured "type": "module" is set in package2/package.json.
2. Built package2 using tsc (npm run build).
3. Attempted to import package2 into Deno without listing package2 dependencies in deno.json.
Thank you.7 replies