@homebound/beam 2.171.2 → 2.172.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.
- package/README.md +0 -20
- package/package.json +4 -5
- package/dist/index.css +0 -768
- package/dist/index.css.map +0 -7
- package/dist/index.mjs +0 -76629
- package/dist/index.mjs.map +0 -7
package/README.md
CHANGED
|
@@ -52,23 +52,3 @@ Our proposal for solving this tension is to adopt a radically different model th
|
|
|
52
52
|
"Adopters" of Beam should of course contribute back bug fixes and feature improvements; but they should also feel free (and encouraged) to run their own company-specific forks, and "customize by changing the source".
|
|
53
53
|
|
|
54
54
|
In this way, Beam should be seen as a place to "copy & paste" start from, rather than a project that will have 1,000s of npm downloads, and 100s of companies all collaborating on getting this _one_ `TextField` implementation to behave in the 101 different ways that they each want.
|
|
55
|
-
|
|
56
|
-
## Bundling
|
|
57
|
-
|
|
58
|
-
Beam provides both CommonJS and ESM artifacts.
|
|
59
|
-
|
|
60
|
-
The CommonJS artifacts are the output of the TypeScript compiler, are not bundled, and are intended to be used downstream for unit testing i.e. in Jest.
|
|
61
|
-
|
|
62
|
-
The ESM artifacts are from esbuild, and are bundled, and instead to be used for downstream bundling, i.e. in create-react-app/vitejs.
|
|
63
|
-
|
|
64
|
-
In terms of pros/cons of bundling:
|
|
65
|
-
|
|
66
|
-
- Pro: The biggest pro is the `esbuild` also bundles our CSS into `dist/index.css`, which we can refer to using `style: dist/index.css` in our `package.json`.
|
|
67
|
-
|
|
68
|
-
Without this bundled CSS, vitejs was unable to rewrite the `require(./DateField.css)` line, and we were having to patch around it.
|
|
69
|
-
|
|
70
|
-
Granted, a) we really don't use a lot of external file CSS files anyway, and b) we could bundle _just_ our CSS.
|
|
71
|
-
|
|
72
|
-
- Pro: The bundle is already ESM, which should "make life easier" (admittedly kinda vague) for vitejs downstream.
|
|
73
|
-
|
|
74
|
-
- (Non-con): I'd thought that a single `index.mjs` would not get tree-shaken, but shaking happens at the `export`-d symbol level and not a file level, so we should be fine.
|
package/package.json
CHANGED
|
@@ -1,13 +1,10 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@homebound/beam",
|
|
3
|
-
"version": "2.
|
|
3
|
+
"version": "2.172.0",
|
|
4
4
|
"author": "Homebound",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"main": "dist/index.js",
|
|
7
|
-
"module": "dist/index.mjs",
|
|
8
|
-
"style": "dist/index.css",
|
|
9
7
|
"typings": "dist/index.d.ts",
|
|
10
|
-
"sideEffects": false,
|
|
11
8
|
"repository": {
|
|
12
9
|
"type": "git",
|
|
13
10
|
"url": "https://github.com/homebound-team/beam"
|
|
@@ -17,6 +14,9 @@
|
|
|
17
14
|
"!dist/**/*.{stories,test}.*",
|
|
18
15
|
"!dist/setupTests.*"
|
|
19
16
|
],
|
|
17
|
+
"engines": {
|
|
18
|
+
"node": ">=16.4.0"
|
|
19
|
+
},
|
|
20
20
|
"scripts": {
|
|
21
21
|
"start": "yarn storybook",
|
|
22
22
|
"build": "yarn copy && ttsc",
|
|
@@ -105,7 +105,6 @@
|
|
|
105
105
|
"babel-loader": "^8.2.2",
|
|
106
106
|
"chromatic": "^5.9.2",
|
|
107
107
|
"conventional-changelog-conventionalcommits": "^4.5.0",
|
|
108
|
-
"esbuild": "^0.15.5",
|
|
109
108
|
"eslint": "^7.21.0",
|
|
110
109
|
"eslint-config-prettier": "^8.1.0",
|
|
111
110
|
"eslint-config-react-app": "^6.0.0",
|