130 introduced "BREAKING CHANGES package is now ESM" which causes import problems in calling packages when using the tag-and-release script (I tested this locally with another repo), so I reverted.
Closes #134 - @Siegrift I agree with your comment that passing the path is easiest and most flexible. In my local testing this does read from the right package.json
130 introduced "BREAKING CHANGES package is now ESM" which causes import problems in calling packages when using the tag-and-release script (I tested this locally with another repo), so I reverted.
Closes #134 - @Siegrift I agree with your comment that passing the path is easiest and most flexible. In my local testing this does read from the right
package.json