jest-did-matcher not published about did-test-suite

[BernhardFuchs]

@shigeya Thx for the quick fix. The Dockerfile works now and the image is deployable. Closing this.

[shigeya]

It is intentionally not published and locally referenced. I was not aware of the issues. Will look into the issues. thanks.

[shigeya]

@OR13 I want to hear your opinion. As a solution to this issue, in PR #70, I tweaked Dockerfile and docker-compose to include both packages.

I don't like to see babel to create ./dist in the image, but I couldn't find a solution. It may be cleaner to separately publish package, but then, we have to manage two separate repositories.

Which do you prefer?

[OR13]

@shigeya its very common to publish multiple npm packages from the same repo with lerna / yarn...

• https://github.com/transmute-industries/did-core/tree/main/packages
• https://github.com/vuejs/vue/tree/dev/packages
• https://github.com/facebook/react/tree/master/packages

However, these approaches generally assume some burden on the maintainers...

I would be happy to take jest-did-matcher -> @did-core/jest-did-matcher , here:

https://github.com/transmute-industries/did-core/tree/main/packages

I think for now, its better to keep everything unpublished and linked with lerna where it is.

[shigeya]

@OR13 I see. Then, let's keep the package stay in the local repository. Now, Is PR #70 reasonable?

[shigeya]

@BernhardFuchs We changed jest-did-matcher to be included as part of the docker image (see PR #70 for the changes). Would you please test and confirm it's working for you?