Interface Merging from Linked Dependency

[FlorianRappl]

It seems that interface merging is not picked up when a dependency is installed via npm link.

[FlorianRappl]

I think this is not possible from a TypeScript perspective. The reason is that the decl. merging works against the name (path) of a module. When I did that locally, my symlinked plugin retrieved piral-core (and all its modules) locally, i.e., from a different path, than the app shell. Since they are not sharing the same project they have different dependencies (they may be the same functionally, but they have different paths).

[FlorianRappl]

Maybe someone knows an answer to this.

(I also tried switching the preserveSymlinks option.)

[MattShrider]

I think this will be a hard problem to get around, and isn't limited to Piral. I believe it is the same problem as https://reactjs.org/warnings/invalid-hook-call-warning.html#duplicate-react.
I didn't get those same errors. (An issue with related content: facebook/react#13991)

A workaround is to npm link ../shell/node_modules/piral-core from the plugin (From within your piral-instance's node_modules folder), but that isn't a great flow.

//piral-instance/index.tsx
cd node_modules/piral-oidc/lib
npm link ../../piral-core