@teambit/legacy-bit-id 1.0.3 → 1.0.4

package/dist/exceptions/invalid-scope-name-from-remote.d.ts

@@ -1,4 +1,5 @@
 import { BitError } from '@teambit/bit-error';
 export default class InvalidScopeNameFromRemote extends BitError {
+    readonly scopeName: string;
     constructor(scopeName: string);
 }

package/dist/exceptions/invalid-scope-name-from-remote.js

@@ -16,6 +16,7 @@ class InvalidScopeNameFromRemote extends _bitError().BitError {
     super(`cannot find scope '${scopeName}'.
 if you are targeting a self-hosted scope, please ensure the scope is configured in your remotes (via "bit remote" command) and that the scope name is correct.
 if this is a scope on bit.cloud please add the organization name before the scope (yourOrg.some-scope-name)`);
+    this.scopeName = scopeName;
   }
 }
 exports.default = InvalidScopeNameFromRemote;

package/dist/exceptions/invalid-scope-name-from-remote.js.map

@@ -1 +1 @@
-{"version":3,"names":["_bitError","data","require","InvalidScopeNameFromRemote","BitError","constructor","scopeName","exports","default"],"sources":["invalid-scope-name-from-remote.ts"],"sourcesContent":["import { BitError } from '@teambit/bit-error';\n\nexport default class InvalidScopeNameFromRemote extends BitError {\n  constructor(scopeName: string) {\n    super(`cannot find scope '${scopeName}'.\nif you are targeting a self-hosted scope, please ensure the scope is configured in your remotes (via \"bit remote\" command) and that the scope name is correct.\nif this is a scope on bit.cloud please add the organization name before the scope (yourOrg.some-scope-name)`);\n  }\n}\n"],"mappings":";;;;;;AAAA,SAAAA,UAAA;EAAA,MAAAC,IAAA,GAAAC,OAAA;EAAAF,SAAA,YAAAA,CAAA;IAAA,OAAAC,IAAA;EAAA;EAAA,OAAAA,IAAA;AAAA;AAEe,MAAME,0BAA0B,SAASC,oBAAQ,CAAC;EAC/DC,WAAWA,CAACC,SAAiB,EAAE;IAC7B,KAAK,CAAE,sBAAqBA,SAAU;AAC1C;AACA,4GAA4G,CAAC;EAC3G;AACF;AAACC,OAAA,CAAAC,OAAA,GAAAL,0BAAA"}
+{"version":3,"names":["_bitError","data","require","InvalidScopeNameFromRemote","BitError","constructor","scopeName","exports","default"],"sources":["invalid-scope-name-from-remote.ts"],"sourcesContent":["import { BitError } from '@teambit/bit-error';\n\nexport default class InvalidScopeNameFromRemote extends BitError {\n  constructor(readonly scopeName: string) {\n    super(`cannot find scope '${scopeName}'.\nif you are targeting a self-hosted scope, please ensure the scope is configured in your remotes (via \"bit remote\" command) and that the scope name is correct.\nif this is a scope on bit.cloud please add the organization name before the scope (yourOrg.some-scope-name)`);\n  }\n}\n"],"mappings":";;;;;;AAAA,SAAAA,UAAA;EAAA,MAAAC,IAAA,GAAAC,OAAA;EAAAF,SAAA,YAAAA,CAAA;IAAA,OAAAC,IAAA;EAAA;EAAA,OAAAA,IAAA;AAAA;AAEe,MAAME,0BAA0B,SAASC,oBAAQ,CAAC;EAC/DC,WAAWA,CAAUC,SAAiB,EAAE;IACtC,KAAK,CAAE,sBAAqBA,SAAU;AAC1C;AACA,4GAA4G,CAAC;IAAC,KAHvFA,SAAiB,GAAjBA,SAAiB;EAItC;AACF;AAACC,OAAA,CAAAC,OAAA,GAAAL,0BAAA"}

package/exceptions/invalid-scope-name-from-remote.ts

@@ -1,7 +1,7 @@
 import { BitError } from '@teambit/bit-error';
 
 export default class InvalidScopeNameFromRemote extends BitError {
-  constructor(scopeName: string) {
+  constructor(readonly scopeName: string) {
     super(`cannot find scope '${scopeName}'.
 if you are targeting a self-hosted scope, please ensure the scope is configured in your remotes (via "bit remote" command) and that the scope name is correct.
 if this is a scope on bit.cloud please add the organization name before the scope (yourOrg.some-scope-name)`);

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "@teambit/legacy-bit-id",
-  "version": "1.0.3",
+  "version": "1.0.4",
   "homepage": "https://bit.cloud/teambit/component/legacy-bit-id",
   "main": "dist/index.js",
   "componentId": {
     "scope": "teambit.component",
     "name": "legacy-bit-id",
-    "version": "1.0.3"
+    "version": "1.0.4"
   },
   "dependencies": {
     "decamelize": "1.2.0",
@@ -30,7 +30,7 @@
     "@types/testing-library__jest-dom": "5.9.5"
   },
   "peerDependencies": {
-    "@teambit/legacy": "1.0.578",
+    "@teambit/legacy": "1.0.584",
     "react": "^16.8.0 || ^17.0.0",
     "react-dom": "^16.8.0 || ^17.0.0"
   },