I am creating an extension for our company containing multiple build/release tasks. They have some shared code which I wanted to make available to my co-workers as an NPM package as well as use in my own tasks.

I therefor created a folder next to my task folders containing the shared code and configured it as a stand alone NPM package. I then linked it to my tasks by using the "npm link" statement. This creates a symbolic link (as I understand) in the node_modules folder to the actual package location on my hard drive.

When running the 'tfx extension create' or 'tfx extension publish' commands the error from the issue title appears. In my understanding this is caused by the symbolic link which tfx can't traverse when building the package.

As a work-around I decided to not use a linked npm package but just reference the files directly and include them all in the extension. However, since the common code is outside the root of each of the tasks, the tasks fail when run after publish.

I feel the first issue should be addressed, but I understand that this might not happen overnight. So any help with a fix for my workaround (or any guidance of reusing code between multiple different tasks) you folks could point me to would be much appreciated

Kind regards,

Jeroen Vos