chore: disable npmjs proxy for local packages (verdaccio`)

`0.0.0-e2e` was accidentally published to NPM, so we must not proxy our local packages to avoid conflicts

.verdaccio/config.yml

@@ -8,13 +8,17 @@ uplinks:
     maxage: 60m
 
 packages:
+  '@nxrocks/*':
+    access: $all
+    publish: $all
+    # proxy: npmjs <-- disable this, because version `0.0.0-e2e` of `@nxrocks/*` packages was accidentally published to NPM 🤦🏿‍♂️ (it makes no sense to proxy them anyway)
+
   '**':
     # give all users (including non-authenticated users) full access
     # because it is a local registry
     access: $all
     publish: $all
     unpublish: $all
-
     # if package is not available locally, proxy requests to npm registry
     proxy: npmjs
 

tools/scripts/start-local-registry.ts

@@ -33,9 +33,9 @@ export default async () => {
     gitCommit: false,
     gitTag: false,
     firstRelease: true,
-    //generatorOptionsOverrides: {
-    //  skipLockFileUpdate: true,
-    //},
+    generatorOptionsOverrides: {
+      skipLockFileUpdate: true,
+    },
   });
   await releasePublish({
     tag: 'e2e',

unpublish

@@ -0,0 +1,19 @@
+npm login
+
+npm unpublish create-nx-spring-boot@"$1" --force --verbose
+npm unpublish create-nx-micronaut@"$1" --force --verbose
+npm unpublish create-nx-quarkus@"$1" --force --verbose
+npm unpublish create-nx-flutter@"$1" --force --verbose
+npm unpublish create-nx-ktor@"$1" --force --verbose
+
+npm unpublish @nxrocks/nx-spring-boot@"$1" --force --verbose
+npm unpublish @nxrocks/nx-micronaut@"$1" --force --verbose
+npm unpublish @nxrocks/nx-quarkus@"$1" --force --verbose
+npm unpublish @nxrocks/nx-ktor@"$1" --force --verbose
+npm unpublish @nxrocks/nx-flutter@"$1" --force --verbose
+npm unpublish @nxrocks/nx-melos@"$1" --force --verbose
+
+npm unpublish @nxrocks/common-jvm@"$1" --force --verbose
+npm unpublish @nxrocks/common-cli@"$1" --force --verbose
+
+npm unpublish @nxrocks/common@"$1" --force --verbose