@junoflow/cli 0.1.1 → 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 (2) hide show
  1. package/eslint.config.js +12 -13
  2. package/package.json +2 -2
package/eslint.config.js CHANGED
@@ -4,17 +4,18 @@ import juno from '@junoflow/eslint-plugin';
4
4
  /**
5
5
  * The lint preset for an integration project.
6
6
  *
7
- * It enables exactly the rules Juno enforces server-side for an integration —
8
- * `no-juno-sdk-import` and nothing else. The flow-only rules
9
- * (`no-dynamic-step-id`, `no-sleep-in-step`) are about `step.run`, which
10
- * integrations do not have; enabling them here would report on code that is
11
- * fine.
7
+ * The rules are not listed here. They come from the plugin's `rulesets.json`,
8
+ * which Juno's verify step reads too — so this preset and the server enable the
9
+ * same set by construction rather than by two lists someone has to keep equal.
10
+ * The flow rules are a different set (`configs.flow`) and are not enabled here:
11
+ * they are about `step.run` and the replay contract, which integrations do not
12
+ * have, and reporting them would flag code that is fine.
12
13
  *
13
- * The one accepted asymmetry: Juno lints the **bundled output** (that is how
14
- * `no-juno-sdk-import` catches a surviving `require`), while this lints your
15
- * **source**. Both catch it; they catch it differently, and the rule knows both
16
- * spellings. It is also why only this half needs a TypeScript parser — by the
17
- * time the server lints, esbuild has already turned it into JavaScript.
14
+ * The one accepted asymmetry: Juno transpiles your source before linting it,
15
+ * because eslint's default parser cannot read TypeScript and putting a parser
16
+ * in the trusted deploy path is a cost it declines to pay. This half has a
17
+ * TypeScript parser and lints the real thing, so a diagnostic here carries the
18
+ * exact line. Both ends run the same rules over the same code.
18
19
  *
19
20
  * `tsconfig.base.json` is the other half of the preset, and a Go test asserts
20
21
  * it matches what Juno type-checks with.
@@ -31,8 +32,6 @@ export default [
31
32
  sourceType: 'module',
32
33
  },
33
34
  plugins: { juno },
34
- rules: {
35
- 'juno/no-juno-sdk-import': 'error',
36
- },
35
+ rules: { ...juno.configs.integration },
37
36
  },
38
37
  ];
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@junoflow/cli",
3
- "version": "0.1.1",
3
+ "version": "0.1.3",
4
4
  "description": "Command line tools for developing Juno integrations",
5
5
  "license": "MIT",
6
6
  "repository": {
@@ -32,7 +32,7 @@
32
32
  "node": ">=20"
33
33
  },
34
34
  "dependencies": {
35
- "@junoflow/eslint-plugin": "0.1.0",
35
+ "@junoflow/eslint-plugin": "0.1.2",
36
36
  "@typescript-eslint/parser": "^8.0.0"
37
37
  },
38
38
  "devDependencies": {