bestax-migrate 2.2.1 → 2.3.0

package/dist/sources/bloomer/styles.d.ts

@@ -0,0 +1,13 @@
+/**
+ * Stylesheet migration for bloomer apps.
+ *
+ * Same shared factory as every other source — the Bulma 0.9 → v1 rewriting is
+ * identical. What differs is that bloomer ships no stylesheet of its own: it
+ * never depended on Bulma, and its README tells the app to install `bulma`
+ * and import it directly. So there is no source root stylesheet to replace
+ * (`rootStylesheetSuffixes` is empty, which the factory tolerates), and the
+ * pass only ever rewrites the app's own `bulma/…` imports — which, coming
+ * from the 0.6 era, are older than anything the 0.9 → v1 guide describes.
+ */
+export declare const transformStyles: import("../../types.js").StylesTransform;
+//# sourceMappingURL=styles.d.ts.map

package/dist/sources/bloomer/styles.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"styles.d.ts","sourceRoot":"","sources":["../../../src/sources/bloomer/styles.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAIH,eAAO,MAAM,eAAe,0CAI1B,CAAC"}

package/dist/sources/bloomer/styles.js

@@ -0,0 +1,17 @@
+/**
+ * Stylesheet migration for bloomer apps.
+ *
+ * Same shared factory as every other source — the Bulma 0.9 → v1 rewriting is
+ * identical. What differs is that bloomer ships no stylesheet of its own: it
+ * never depended on Bulma, and its README tells the app to install `bulma`
+ * and import it directly. So there is no source root stylesheet to replace
+ * (`rootStylesheetSuffixes` is empty, which the factory tolerates), and the
+ * pass only ever rewrites the app's own `bulma/…` imports — which, coming
+ * from the 0.6 era, are older than anything the 0.9 → v1 guide describes.
+ */
+import { makeStylesTransform } from '../_shared/make-styles-transform.js';
+export const transformStyles = makeStylesTransform({
+    packageName: 'bloomer',
+    guideUrl: 'https://bestax.io/docs/guides/getting-started/migration/bloomer',
+    rootStylesheetSuffixes: [],
+});

package/dist/sources/bloomer/transform.d.ts

@@ -0,0 +1,27 @@
+/**
+ * The bloomer (0.6) → @allxsmith/bestax-bulma transform.
+ *
+ * Passes, in order:
+ *   1. resolve imports (named/namespace) and `const { Item } = Card`-style
+ *      destructuring into canonical bloomer component paths
+ *   2. per-element: structural special → rename → helper flattening
+ *      (isDisplay / isHidden / Column sizes) → component prop map →
+ *      universal helper props
+ *   3. rewrite imports: drop bloomer, add one merged bestax-bulma import; keep
+ *      a trimmed bloomer import (with a TODO) only for components that have
+ *      no bestax equivalent (Tile, the Nav family, …)
+ *
+ * Anything unsafe gets a `// TODO(bestax-migrate)` comment on the enclosing
+ * statement plus an entry in the run report.
+ *
+ * Next to the bloomer transform this is the plain case: bloomer has no helper
+ * props that become wrapping components, no stylesheet of its own and no
+ * extension packages — so there is no wrapping pass and the CSS pass only
+ * ever sees the app's own Bulma import. Every bloomer export is a flat name,
+ * and most of them rename onto a dotted bestax compound; the rename and
+ * value-reference passes below build those from the mapping's `target`.
+ */
+import type { API, FileInfo } from 'jscodeshift';
+import type { TransformOptions } from '../../types.js';
+export default function transform(fileInfo: FileInfo, api: API, options?: TransformOptions): string | undefined;
+//# sourceMappingURL=transform.d.ts.map

package/dist/sources/bloomer/transform.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"transform.d.ts","sourceRoot":"","sources":["../../../src/sources/bloomer/transform.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;GAsBG;AAEH,OAAO,KAAK,EAAE,GAAG,EAAE,QAAQ,EAAE,MAAM,aAAa,CAAC;AACjD,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,gBAAgB,CAAC;AAuDvD,MAAM,CAAC,OAAO,UAAU,SAAS,CAC/B,QAAQ,EAAE,QAAQ,EAClB,GAAG,EAAE,GAAG,EACR,OAAO,GAAE,gBAAqB,GAC7B,MAAM,GAAG,SAAS,CA06BpB"}