chore: check publishConfig.directory when releasing

.scripts/release.js

@@ -236,17 +236,20 @@ async function publishPackage(pkgName, version, runIfNotDry) {
 
   step(`Publishing ${pkgName}...`);
 
+  const publishDir = pkg.publishConfig?.directory;
+
   try {
     await runIfNotDry(
       // use of yarn is intentional here as we rely on its publishing behavior.
       'yarn',
       [
-        'publish',
+        ...(publishDir ? ['publish', publishDir] : ['publish']),
         '--new-version',
         version,
         ...(releaseTag ? ['--tag', releaseTag] : []),
         '--access',
         'public',
+        ...(publishDir ? ['--no-git-tag-version'] : []),
       ],
       {
         cwd: pkgRoot,

package.json

@@ -1,6 +1,6 @@
 {
   "name": "vime",
-  "version": "5.0.35",
+  "version": "5.2.0",
   "private": true,
   "license": "MIT",
   "type": "module",

packages/angular/projects/vime/package.json

@@ -25,15 +25,16 @@
     "postinstall": "node ./.scripts/validate.cjs"
   },
   "peerDependencies": {
+    "@vime/core": "^5.0.0",
     "@angular/common": "^11.0.4",
     "@angular/core": "^11.0.4",
     "rxjs": "^6.6.2"
   },
   "dependencies": {
-    "@vime/core": "^5.0.0",
     "tslib": "^2.0.0"
   },
   "devDependencies": {
+    "@vime/core": "^5.0.0",
     "rxjs": "^6.6.2"
   },
   "publishConfig": {