@opentelemetry/test-utils dependency

[nozik]

Several of the plugins/instrumentations in the js-contrib repository (e.g., opentelemetry-instrumentation-redis) depend on the @opentelemetry/test-utils package, which is included as part of the repository but not released publicly to npm (-> and therefore yarn install fails for such instrumentations). How can I start working with this dependency?

I'm not sure this is the correct place to ask, please point at the right direction if necessary.

Much appreciated.

[dyladan]

It is only included as a development dependency. When you set up the repository, local dependencies are already linked by lerna. Are you talking about using it from an external repository?

[nozik]

In a sense, yes. I was trying to work on each of the instrumentation classes independently of the entire js-contrib repository. If if understand you correctly, that's not how the repository is defined, and is only enabled by using lerna.

[rauno56]

You are right, @nozik. Those are linked together by lerna. The step is included in npm install lifecycle scripts so once you run npm install in the contrib project root, redis instrumentation works as expected.
A workaround is to manually link the dev dependency to a local package by replacing the version of @opentelemetry/test-utils in the package.json of the redis instrumentation:

    "@opentelemetry/test-utils": "file:../../../packages/opentelemetry-test-utils",

In that case npm install in the redis folder works without lerna.

[nozik]

That was the solution I applied as well. I'll just keep doing it to keep things simple. Thanks @rauno56.

[rauno56]

Actually, why don't we publish it @dyladan? I cannot see any downside in that. I'd perhaps change the name to something more specific. For example "contrib-test-utils".

[aabmass]

Would bootstrapping just the package you are interested in work? I.e. lerna bootstrap --scope @opentelemetry/instrumentation-redis

I've also seen lerna fail with this approach, so ymmv