@ploaness/config 1.10.0 → 1.11.0

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 (61) hide show
  1. package/dist/a11y.d.ts +4 -2
  2. package/dist/a11y.d.ts.map +1 -1
  3. package/dist/a11y.js +7 -17
  4. package/dist/a11y.js.map +1 -1
  5. package/dist/eslint-core.d.ts +4 -0
  6. package/dist/eslint-core.d.ts.map +1 -1
  7. package/dist/eslint-core.js +28 -6
  8. package/dist/eslint-core.js.map +1 -1
  9. package/dist/eslint-immutability.d.ts +4 -0
  10. package/dist/eslint-immutability.d.ts.map +1 -0
  11. package/dist/eslint-immutability.js +66 -0
  12. package/dist/eslint-immutability.js.map +1 -0
  13. package/dist/eslint-javascript-parser.d.ts +3 -0
  14. package/dist/eslint-javascript-parser.d.ts.map +1 -0
  15. package/dist/eslint-javascript-parser.js +35 -0
  16. package/dist/eslint-javascript-parser.js.map +1 -0
  17. package/dist/eslint-library.d.ts.map +1 -1
  18. package/dist/eslint-library.js +9 -7
  19. package/dist/eslint-library.js.map +1 -1
  20. package/dist/eslint.d.ts.map +1 -1
  21. package/dist/eslint.js +6 -3
  22. package/dist/eslint.js.map +1 -1
  23. package/dist/formatting.d.ts +3 -0
  24. package/dist/formatting.d.ts.map +1 -0
  25. package/dist/formatting.js +4 -0
  26. package/dist/formatting.js.map +1 -0
  27. package/dist/playwright.d.ts.map +1 -1
  28. package/dist/playwright.js +16 -4
  29. package/dist/playwright.js.map +1 -1
  30. package/dist/production-build.d.ts +13 -0
  31. package/dist/production-build.d.ts.map +1 -0
  32. package/dist/production-build.js +32 -0
  33. package/dist/production-build.js.map +1 -0
  34. package/dist/production-environment.d.ts +7 -0
  35. package/dist/production-environment.d.ts.map +1 -0
  36. package/dist/production-environment.js +20 -0
  37. package/dist/production-environment.js.map +1 -0
  38. package/dist/production-server.js +3 -19
  39. package/dist/production-server.js.map +1 -1
  40. package/dist/project-settings.d.ts.map +1 -1
  41. package/dist/project-settings.js +21 -3
  42. package/dist/project-settings.js.map +1 -1
  43. package/dist/settle.d.ts +2 -1
  44. package/dist/settle.d.ts.map +1 -1
  45. package/dist/settle.js +44 -1
  46. package/dist/settle.js.map +1 -1
  47. package/dist/vitest-core.d.ts +2 -0
  48. package/dist/vitest-core.d.ts.map +1 -1
  49. package/dist/vitest-core.js +6 -1
  50. package/dist/vitest-core.js.map +1 -1
  51. package/dist/vitest-library.d.ts.map +1 -1
  52. package/dist/vitest-library.js +4 -3
  53. package/dist/vitest-library.js.map +1 -1
  54. package/dist/vitest.d.ts.map +1 -1
  55. package/dist/vitest.js +5 -3
  56. package/dist/vitest.js.map +1 -1
  57. package/package.json +28 -15
  58. package/pins.json +8 -8
  59. package/prettier-scss.json +7 -0
  60. package/stylelint.json +25 -2
  61. package/tsconfig-core.json +1 -1
package/pins.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "$comment": "Everything ploaness pins that it cannot pin by declaring a dependency. A pinned analyzer is a real dependency of a ploaness package, so its version has exactly one source; nothing here can be, because ploaness imports none of it and declaring it would install a second Payload, Next, React, or set of type definitions into a project that already has one - and two copies of @types/react in a single tree is not merely waste, it is a class of type error that reads as the project's fault. This file is that one source instead. It is data rather than code: a group carries the rule that applies to it, so adding one needs no change anywhere else.",
3
3
  "$required": "A group states the member KINDS that must declare it. A kind is derived from what a package declares - Payload, or Next, or neither - never from what it says about itself. The split matters because a workspace holds packages that are not all applications: requiring a shared library to declare Payload would manufacture a dependency the dead-code gate then rightly reports as unused, and requiring a Next frontend to declare Payload would make ploaness dictate an architecture rather than a version. A group required by no kind is matched when a package declares it and forced on nobody, which is how ploaness owns the version of a Postgres driver without deciding that every governed project uses Postgres.",
4
- "packageManager": "pnpm@12.8.1",
4
+ "packageManager": "pnpm@12.14.0",
5
5
  "$engines": "Only `node` is stated here. The pnpm entry is derived from `packageManager` above, because Corepack reads one field and an installer reads the other and two literals for one version will not stay equal - these two had already stopped agreeing in meaning, an exact `pnpm@11.9.0` beside a `>=11` floor.",
6
6
  "engines": {
7
7
  "node": ">=26"
@@ -12,7 +12,7 @@
12
12
  "requiredFor": ["payload"],
13
13
  "why": "The Payload application itself, and the two packages Payload declares as peers. Only a member that IS a Payload application needs any of them; a frontend reading that application over HTTP needs none.",
14
14
  "versions": {
15
- "payload": "3.90.2",
15
+ "payload": "3.91.0",
16
16
  "sharp": "0.35.5",
17
17
  "graphql": "16.14.2"
18
18
  }
@@ -22,9 +22,9 @@
22
22
  "requiredFor": ["payload", "application"],
23
23
  "why": "What any Next application renders with, whether or not Payload is mounted inside it. A public frontend has the same build, the same client bundle and the same React version to agree about.",
24
24
  "versions": {
25
- "next": "16.4.0",
26
- "react": "19.3.0",
27
- "react-dom": "19.3.0",
25
+ "next": "16.4.2",
26
+ "react": "19.3.1",
27
+ "react-dom": "19.3.1",
28
28
  "@types/react": "19.3.0",
29
29
  "@types/react-dom": "19.3.0"
30
30
  }
@@ -34,7 +34,7 @@
34
34
  "requiredFor": ["payload", "application", "library"],
35
35
  "why": "The definitions describing the runtime every governed package compiles against. Pinned for the toolchain's reason rather than the framework's: a type package is an input to tsc, so a patch release changes what type-checks while the project stays unchanged.",
36
36
  "versions": {
37
- "@types/node": "26.6.4"
37
+ "@types/node": "26.6.5"
38
38
  }
39
39
  },
40
40
  {
@@ -43,9 +43,9 @@
43
43
  "versions": {
44
44
  "pg": "8.23.1",
45
45
  "@types/pg": "8.23.1",
46
- "dotenv": "18.0.6",
46
+ "dotenv": "18.0.8",
47
47
  "cross-env": "10.1.0",
48
- "vite": "8.3.3"
48
+ "vite": "8.3.4"
49
49
  }
50
50
  }
51
51
  ]
@@ -0,0 +1,7 @@
1
+ {
2
+ "tabWidth": 4,
3
+ "useTabs": false,
4
+ "printWidth": 120,
5
+ "endOfLine": "lf",
6
+ "singleQuote": true
7
+ }
package/stylelint.json CHANGED
@@ -26,7 +26,12 @@
26
26
  ]
27
27
  }
28
28
  ],
29
- "at-rule-prelude-no-invalid": [true, { "ignoreAtRules": ["media", "apply"] }],
29
+ "at-rule-prelude-no-invalid": [
30
+ true,
31
+ {
32
+ "ignoreAtRules": ["media", "apply"]
33
+ }
34
+ ],
30
35
  "import-notation": "string",
31
36
  "selector-pseudo-class-no-unknown": [
32
37
  true,
@@ -47,5 +52,23 @@
47
52
  "lightness-notation": "number",
48
53
  "hue-degree-notation": "number",
49
54
  "selector-id-pattern": "^(__[a-zA-Z0-9]+|[a-z][a-z0-9]*(-[a-z0-9]+)*)$"
50
- }
55
+ },
56
+ "overrides": [
57
+ {
58
+ "files": ["**/*.scss"],
59
+ "customSyntax": "postcss-scss",
60
+ "plugins": ["stylelint-scss"],
61
+ "rules": {
62
+ "at-rule-no-unknown": null,
63
+ "scss/at-rule-no-unknown": true,
64
+ "at-rule-prelude-no-invalid": null,
65
+ "function-no-unknown": null,
66
+ "scss/function-no-unknown": true,
67
+ "declaration-property-value-no-unknown": null,
68
+ "color-no-invalid-hex": true,
69
+ "no-empty-source": null
70
+ },
71
+ "$comment": "An empty stylesheet is valid: Payload's template provides an empty custom.scss for optional application styles."
72
+ }
73
+ ]
51
74
  }
@@ -9,7 +9,7 @@
9
9
  "strict": true,
10
10
  "noEmit": true,
11
11
  "esModuleInterop": true,
12
- "module": "esnext",
12
+ "module": "preserve",
13
13
  "moduleResolution": "bundler",
14
14
  "resolveJsonModule": true,
15
15
  "isolatedModules": true,