@backstage/eslint-plugin 0.1.3-next.0 → 0.1.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/CHANGELOG.md +6 -0
  2. package/package.json +2 -2
  3. package/rules/no-undeclared-imports.js +1 -1
package/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # @backstage/eslint-plugin
2
2
 
3
+ ## 0.1.3
4
+
5
+ ### Patch Changes
6
+
7
+ - 911c25de59c: Add support for auto-fixing missing imports detected by the `no-undeclared-imports` rule.
8
+
3
9
  ## 0.1.3-next.0
4
10
 
5
11
  ### Patch Changes
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@backstage/eslint-plugin",
3
3
  "description": "Backstage ESLint plugin",
4
- "version": "0.1.3-next.0",
4
+ "version": "0.1.3",
5
5
  "publishConfig": {
6
6
  "access": "public"
7
7
  },
@@ -22,7 +22,7 @@
22
22
  "minimatch": "^5.1.2"
23
23
  },
24
24
  "devDependencies": {
25
- "@backstage/cli": "^0.22.6-next.0",
25
+ "@backstage/cli": "^0.22.6",
26
26
  "eslint": "^8.33.0"
27
27
  }
28
28
  }
package/rules/no-undeclared-imports.js CHANGED
@@ -180,7 +180,7 @@ module.exports = {
180
180
  // The security implication of this is a bit interesting, as crafted add-import
181
181
  // directives could be used to install malicious packages. However, the same is true
182
182
  // for adding malicious packages to package.json, so there's significant difference.
183
- execFileSync('yarn', ['add', ...(flag || []), ...names], {
183
+ execFileSync('yarn', ['add', ...(flag ? [flag] : []), ...names], {
184
184
  cwd: localPkg.dir,
185
185
  stdio: 'inherit',
186
186
  });