@bamboocss/parser 1.34.0 → 1.34.1

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.
package/dist/index.d.cts CHANGED
@@ -137,13 +137,15 @@ declare class Generator extends Context {
137
137
  * Only under `unresolvedToken: 'error'` — see that option for why this one is graded and a
138
138
  * dead binding is not.
139
139
  *
140
- * Read off the decoded sheet rather than accumulated as `transform` runs, and that is the
141
- * load-bearing part. A `Context` outlives rebuilds while the decoder memoizes each atom by
142
- * hash, so on the second build of the same source `transform` is never re-entered: an
143
- * accumulating record either keeps a finding past the edit that fixed it wedging a dev
144
- * server or is cleared and then never refilled, which passes a build whose source is
145
- * still broken. That second one is the worse failure and is what an earlier version of this
146
- * did.
140
+ * Two sources, because neither sees the whole build.
141
+ *
142
+ * **Atomic styles are read off the decoded sheet** rather than accumulated as `transform`
143
+ * runs, and that is the load-bearing part for them. A `Context` outlives rebuilds while the
144
+ * decoder memoizes each atom by hash, so on the second build of the same source `transform`
145
+ * is never re-entered: an accumulating record either keeps a finding past the edit that
146
+ * fixed it — wedging a dev server — or is cleared and then never refilled, which passes a
147
+ * build whose source is still broken. That second one is the worse failure and is what an
148
+ * earlier version of this did.
147
149
  *
148
150
  * `decoder.atomic` has neither problem, because it is not a record of what happened — it is
149
151
  * what the sheet is built from, and each result keeps the `prop` and `value` it was written
@@ -157,6 +159,18 @@ declare class Generator extends Context {
157
159
  * own output. A production build is a fresh process and sees only what its source asked
158
160
  * for.
159
161
  *
162
+ * **Config-derived styles are not in that set at all**, which is the gap this used to have.
163
+ * `globalCss`, the reset, config recipes and compositions serialize through
164
+ * `transformStyles`, and that clones the decoder — so their atoms land in a throwaway and
165
+ * `decoder.atomic` never hears about them. Reading only the sheet made `'error'` *quieter*
166
+ * than the default on exactly those styles: the warning was suppressed in favour of a check
167
+ * that could not see them, so a bad token in `globalCss` warned with the option unset and
168
+ * then passed silently with it set to `'error'`. `utility.unresolvedTokens` is the record of
169
+ * what only `transform` can see; see it for why accumulating is right for that half.
170
+ *
171
+ * Both halves key on `property:path` with shorthands resolved, so a value that does reach
172
+ * both — every atomic style is transformed once before it is memoized — is one finding.
173
+ *
160
174
  * Here rather than beside the asserts in `BambooContext` because this is where the sheet
161
175
  * exists: those all run during extraction, before anything has been decoded. Every path
162
176
  * that emits css comes through `getCss`.
package/dist/index.d.mts CHANGED
@@ -137,13 +137,15 @@ declare class Generator extends Context {
137
137
  * Only under `unresolvedToken: 'error'` — see that option for why this one is graded and a
138
138
  * dead binding is not.
139
139
  *
140
- * Read off the decoded sheet rather than accumulated as `transform` runs, and that is the
141
- * load-bearing part. A `Context` outlives rebuilds while the decoder memoizes each atom by
142
- * hash, so on the second build of the same source `transform` is never re-entered: an
143
- * accumulating record either keeps a finding past the edit that fixed it wedging a dev
144
- * server or is cleared and then never refilled, which passes a build whose source is
145
- * still broken. That second one is the worse failure and is what an earlier version of this
146
- * did.
140
+ * Two sources, because neither sees the whole build.
141
+ *
142
+ * **Atomic styles are read off the decoded sheet** rather than accumulated as `transform`
143
+ * runs, and that is the load-bearing part for them. A `Context` outlives rebuilds while the
144
+ * decoder memoizes each atom by hash, so on the second build of the same source `transform`
145
+ * is never re-entered: an accumulating record either keeps a finding past the edit that
146
+ * fixed it — wedging a dev server — or is cleared and then never refilled, which passes a
147
+ * build whose source is still broken. That second one is the worse failure and is what an
148
+ * earlier version of this did.
147
149
  *
148
150
  * `decoder.atomic` has neither problem, because it is not a record of what happened — it is
149
151
  * what the sheet is built from, and each result keeps the `prop` and `value` it was written
@@ -157,6 +159,18 @@ declare class Generator extends Context {
157
159
  * own output. A production build is a fresh process and sees only what its source asked
158
160
  * for.
159
161
  *
162
+ * **Config-derived styles are not in that set at all**, which is the gap this used to have.
163
+ * `globalCss`, the reset, config recipes and compositions serialize through
164
+ * `transformStyles`, and that clones the decoder — so their atoms land in a throwaway and
165
+ * `decoder.atomic` never hears about them. Reading only the sheet made `'error'` *quieter*
166
+ * than the default on exactly those styles: the warning was suppressed in favour of a check
167
+ * that could not see them, so a bad token in `globalCss` warned with the option unset and
168
+ * then passed silently with it set to `'error'`. `utility.unresolvedTokens` is the record of
169
+ * what only `transform` can see; see it for why accumulating is right for that half.
170
+ *
171
+ * Both halves key on `property:path` with shorthands resolved, so a value that does reach
172
+ * both — every atomic style is transformed once before it is memoized — is one finding.
173
+ *
160
174
  * Here rather than beside the asserts in `BambooContext` because this is where the sheet
161
175
  * exists: those all run during extraction, before anything has been decoded. Every path
162
176
  * that emits css comes through `getCss`.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@bamboocss/parser",
3
- "version": "1.34.0",
3
+ "version": "1.34.1",
4
4
  "description": "The static parser for bamboo css",
5
5
  "homepage": "https://bamboocss.com",
6
6
  "license": "MIT",
@@ -34,17 +34,17 @@
34
34
  "dependencies": {
35
35
  "ts-morph": "28.0.0",
36
36
  "ts-pattern": "5.9.0",
37
- "@bamboocss/config": "^1.34.0",
38
- "@bamboocss/core": "^1.34.0",
39
- "@bamboocss/shared": "1.34.0",
40
- "@bamboocss/logger": "1.34.0",
41
- "@bamboocss/extractor": "1.34.0",
42
- "@bamboocss/types": "1.34.0"
37
+ "@bamboocss/config": "^1.34.1",
38
+ "@bamboocss/core": "^1.34.1",
39
+ "@bamboocss/extractor": "1.34.1",
40
+ "@bamboocss/logger": "1.34.1",
41
+ "@bamboocss/shared": "1.34.1",
42
+ "@bamboocss/types": "1.34.1"
43
43
  },
44
44
  "devDependencies": {
45
- "@bamboocss/generator": "1.34.0",
46
- "@bamboocss/plugin-vue": "1.34.0",
47
- "@bamboocss/plugin-svelte": "1.34.0"
45
+ "@bamboocss/generator": "1.34.1",
46
+ "@bamboocss/plugin-svelte": "1.34.1",
47
+ "@bamboocss/plugin-vue": "1.34.1"
48
48
  },
49
49
  "scripts": {
50
50
  "build": "tsdown src/index.ts --format=esm,cjs --dts",