@osdlc/tiered-dirs 0.0.0-stage → 0.3.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/CHANGELOG.md +99 -0
- package/CONTRIBUTING.md +66 -0
- package/LICENSE-APACHE +202 -0
- package/LICENSE-MIT +21 -0
- package/README.md +422 -2
- package/SECURITY.md +23 -0
- package/dist/base-dirs.d.ts +311 -0
- package/dist/base-dirs.js +477 -0
- package/dist/errors.d.ts +36 -0
- package/dist/errors.js +20 -0
- package/dist/index.d.ts +27 -0
- package/dist/index.js +24 -0
- package/dist/segment.d.ts +17 -0
- package/dist/segment.js +40 -0
- package/dist/tiered-dirs.d.ts +190 -0
- package/dist/tiered-dirs.js +237 -0
- package/package.json +64 -3
package/CHANGELOG.md
ADDED
|
@@ -0,0 +1,99 @@
|
|
|
1
|
+
# Changelog
|
|
2
|
+
|
|
3
|
+
## 0.3.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- 93ca515: First public release. Machine-local directories for one vendor's products, addressed on two axes:
|
|
8
|
+
the tier says who shares the state (the vendor, a suite of products, or one standalone tool), and
|
|
9
|
+
the home says how durable it is (durable, config, cache, state, logs, runtime). The homes come
|
|
10
|
+
from a per-OS table with native or XDG paths, every root can be moved by an override variable,
|
|
11
|
+
and a test runner process gets a scratch root instead of the real home unless `<P>_ROOT` is set
|
|
12
|
+
or `HOME` was moved off the passwd home (see the README for the rules).
|
|
13
|
+
|
|
14
|
+
The additions:
|
|
15
|
+
|
|
16
|
+
- `TieredDirs`, with `vendor()`, `suite(key)` and `standalone(tool)`, which return a `Tier`. A
|
|
17
|
+
`Tier` gives a `Dir` for each home: `durable()`, `config()`, `cache()`, `state()`, `logs()`,
|
|
18
|
+
`runtime()`, or `home(name)`. `Dir.scoped(kind, key)` and `Dir.app(app)` narrow a directory.
|
|
19
|
+
`TieredDirs.scratch()` gives the platform temp directory, outside both axes.
|
|
20
|
+
- `TieredDirs.fromEnv(vendor, vars, opts)` and `systemBaseDirs(vars, opts)` resolve the base
|
|
21
|
+
directories from the environment once. `rootedBaseDirs(root)` lays every root out under one
|
|
22
|
+
directory, and `xdgBaseDirs(home, env)` builds the XDG table under any home.
|
|
23
|
+
- `envVars(prefix)` names the override variables: `<P>_ROOT`, `<P>_<HOME>_DIR`,
|
|
24
|
+
`<P>_SCRATCH_DIR`, `<P>_REQUIRE_OVERRIDE` and `<P>_CONVENTION`. `overrideVars(vars)` lists the
|
|
25
|
+
ones that move a directory. `isOverridden(vars, env)` says whether any of them is set to a
|
|
26
|
+
non-empty value.
|
|
27
|
+
- Conventions: `native` (the default) or `xdg`, chosen by the caller or by `<P>_CONVENTION`.
|
|
28
|
+
`parseConvention(value)` parses one exactly, untrimmed.
|
|
29
|
+
- `isValidSegment(key)`, the rule every caller-supplied segment must pass. `state`, `logs` and
|
|
30
|
+
`run` are reserved.
|
|
31
|
+
- `isVendorBundleId(vendor, bundleId)`, the check `TieredDirs.isVendorBundleId` makes, for a
|
|
32
|
+
caller with no `TieredDirs`.
|
|
33
|
+
- `TieredDirsError`, the one error class the package throws. Its `code` is one of
|
|
34
|
+
`MISSING_BASE_DIR`, `RELATIVE_OVERRIDE`, `OVERRIDE_REQUIRED`, `INVALID_CONVENTION` and
|
|
35
|
+
`INVALID_KEY`.
|
|
36
|
+
- `ResolveOptions`, the options of `systemBaseDirs` and `TieredDirs.fromEnv`. `testRoot: false`
|
|
37
|
+
skips the test-root default; `<P>_ROOT` and `<P>_REQUIRE_OVERRIDE` still apply.
|
|
38
|
+
- `testRoot()`, the per-process scratch root in a test runner process, else `undefined`.
|
|
39
|
+
- The types `BaseDirs`, `EnvVars`, `Home`, `Convention`, `TierKind`, `ResolveOptions` and
|
|
40
|
+
`TieredDirsErrorCode`, and the lists `HOMES`, `CONVENTIONS` and `TIER_KINDS`. A minor release
|
|
41
|
+
may add a member to `TierKind`, `Convention` or `TieredDirsErrorCode`, or a name to `EnvVars`.
|
|
42
|
+
- The test-root rule recognises a Vitest worker (`VITEST_WORKER_ID` or `VITEST_POOL_ID` set, and
|
|
43
|
+
the entry point in the `vitest` package's `dist/workers` folder, or tinypool's
|
|
44
|
+
`dist/entry/process.js` or `dist/entry/worker.js` on Vitest 3 and earlier), as well as `NODE_ENV=test`,
|
|
45
|
+
`node --test` and Bun. A child process a test spawns still gets no default.
|
|
46
|
+
|
|
47
|
+
Changes:
|
|
48
|
+
|
|
49
|
+
- `Dir` and `Tier` are exported as types only. A caller gets a value from the checked methods
|
|
50
|
+
(`TieredDirs.vendor()`, `suite()`, `standalone()`, `scratch()`, `Tier.home()` and `Dir.scoped()`
|
|
51
|
+
or `app()`), never from a constructor.
|
|
52
|
+
- Every `BaseDirs` field is `readonly`.
|
|
53
|
+
- Aligned with the Rust crate tiered-dirs 0.3.0.
|
|
54
|
+
|
|
55
|
+
## History before the first public release
|
|
56
|
+
|
|
57
|
+
These versions were never published. They are rebuilt from the git history.
|
|
58
|
+
|
|
59
|
+
### [0.2.0] - 2026-10-17 (unpublished)
|
|
60
|
+
|
|
61
|
+
#### Added
|
|
62
|
+
|
|
63
|
+
- A `state` home: `state` in `Home` and `HOMES`, `Tier.state()`, `<P>_STATE_DIR` and
|
|
64
|
+
`<root>/state`. It is the XDG state home on Linux and Application Support on macOS. On Windows
|
|
65
|
+
it is `%LOCALAPPDATA%\state`, beside each tier's cache folder, never the same folder.
|
|
66
|
+
- Conventions: `native` (the default) or `xdg`, through `systemBaseDirs(vars, { convention })`
|
|
67
|
+
and `TieredDirs.fromEnv(vendor, vars, { convention })`, with `Convention` and `CONVENTIONS`.
|
|
68
|
+
`xdg` gives the XDG paths on macOS too; Linux is the same under both, and on Windows `xdg`
|
|
69
|
+
means `native`. A relative `XDG_*` value is ignored and `~` is not expanded.
|
|
70
|
+
- `xdgBaseDirs(home, env)` builds the XDG table under any home.
|
|
71
|
+
- `<P>_CONVENTION=native|xdg` overrides the caller's convention; any other value throws
|
|
72
|
+
`TieredDirsError`.
|
|
73
|
+
|
|
74
|
+
#### Changed
|
|
75
|
+
|
|
76
|
+
- Breaking: `Home` and `HOMES` gain `state`. An exhaustive `switch` over `Home` must handle it.
|
|
77
|
+
- Breaking: `EnvVars` has `state` and `convention` names, and `BaseDirs` has a `state` root. An
|
|
78
|
+
object built by hand needs them; build `EnvVars` with `envVars()`.
|
|
79
|
+
- Breaking: `state`, `logs` and `run` are reserved segment names, refused in any case, so no tier
|
|
80
|
+
lands on another home's root. `suite`, `standalone`, `Dir.scoped`, `Dir.app` and
|
|
81
|
+
`isValidSegment` refuse them.
|
|
82
|
+
|
|
83
|
+
### [0.1.0] - 2026-10-06 (unpublished)
|
|
84
|
+
|
|
85
|
+
#### Added
|
|
86
|
+
|
|
87
|
+
- `TieredDirs`, `Tier` and `Dir`: directories addressed by tier (`vendor()`, `suite(key)`,
|
|
88
|
+
`standalone(tool)`) and home (`durable`, `config`, `cache`, `logs`, `runtime`), plus an
|
|
89
|
+
untiered `scratch()` root. Every builder returns a new value, and every caller-supplied segment
|
|
90
|
+
is checked to be one safe path segment.
|
|
91
|
+
- `systemBaseDirs` and `TieredDirs.fromEnv`: the per-OS table resolved once, with logs in
|
|
92
|
+
`~/Library/Logs` on macOS and runtime under the durable home where the platform has none. Every
|
|
93
|
+
input is injectable: the platform, the environment, the home directory and single roots.
|
|
94
|
+
- Override variables under a caller-chosen prefix (`envVars`, `overrideVars`), and
|
|
95
|
+
`rootedBaseDirs` for the layout `<P>_ROOT` selects.
|
|
96
|
+
- Test isolation: in a test runner process with `<P>_ROOT` unset, the root reads as a scratch
|
|
97
|
+
directory unique to the process, and `<P>_REQUIRE_OVERRIDE` turns a fallback to the real home
|
|
98
|
+
into an error.
|
|
99
|
+
- `TieredDirsError`, `isValidSegment`, `HOMES` and `TIER_KINDS`.
|
package/CONTRIBUTING.md
ADDED
|
@@ -0,0 +1,66 @@
|
|
|
1
|
+
# Contributing
|
|
2
|
+
|
|
3
|
+
Thanks for your interest in `@osdlc/tiered-dirs`.
|
|
4
|
+
|
|
5
|
+
## Issues
|
|
6
|
+
|
|
7
|
+
Report bugs and ask for features in the
|
|
8
|
+
[issue tracker](https://github.com/osdlc/osdlc/issues). For a bug, include the
|
|
9
|
+
library version, your runtime and its version, your operating system, and the
|
|
10
|
+
call and inputs that misbehave. Report security problems privately. See
|
|
11
|
+
[SECURITY.md](./SECURITY.md).
|
|
12
|
+
|
|
13
|
+
## Pull requests
|
|
14
|
+
|
|
15
|
+
This package lives in [osdlc/osdlc](https://github.com/osdlc/osdlc) under
|
|
16
|
+
`packages/ts/tiered-dirs`. Open pull requests there. They are reviewed and merged
|
|
17
|
+
there.
|
|
18
|
+
|
|
19
|
+
## Running the tests
|
|
20
|
+
|
|
21
|
+
The repository is a pnpm workspace. Install from the repository root, then
|
|
22
|
+
work in the package directory. The tests run on [Vitest](https://vitest.dev)
|
|
23
|
+
under Node 22.12 or later.
|
|
24
|
+
|
|
25
|
+
```sh
|
|
26
|
+
pnpm install
|
|
27
|
+
cd packages/ts/tiered-dirs
|
|
28
|
+
pnpm test
|
|
29
|
+
```
|
|
30
|
+
|
|
31
|
+
`pnpm run coverage` reports test coverage.
|
|
32
|
+
|
|
33
|
+
`pnpm run build` compiles the package to `dist/`. `pnpm run smoke` runs
|
|
34
|
+
`tests/smoke.mjs`, a short check of the built package under Node. Build first.
|
|
35
|
+
It is not published.
|
|
36
|
+
|
|
37
|
+
Other checks:
|
|
38
|
+
|
|
39
|
+
```sh
|
|
40
|
+
pnpm run typecheck
|
|
41
|
+
pnpm run lint
|
|
42
|
+
pnpm run format:check
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
## The parity fixture
|
|
46
|
+
|
|
47
|
+
`packages/rust/tiered-dirs/tests/fixtures/parity.json` is read by this
|
|
48
|
+
package's `tests/parity.test.ts` and by the Rust crate's `tests/parity.rs`.
|
|
49
|
+
A new path shape goes into that file first, so both suites cover it. Neither
|
|
50
|
+
twin may add a shape the other lacks.
|
|
51
|
+
|
|
52
|
+
## Code style
|
|
53
|
+
|
|
54
|
+
- TypeScript, ES modules, and explicit `.ts` import paths.
|
|
55
|
+
- Prettier formats the code and oxlint checks it. Run `pnpm run format` and
|
|
56
|
+
`pnpm run lint` before you commit.
|
|
57
|
+
- Add a test for each behaviour change or bug fix.
|
|
58
|
+
- A new export gets TSDoc and a use in `examples/`, which imports the package
|
|
59
|
+
by name. A test fails if an export has no example.
|
|
60
|
+
- An export's TSDoc says "Stable in 0.x." and the README's Stability section
|
|
61
|
+
lists it. A test checks both.
|
|
62
|
+
- Path assertions must not depend on the separator: compare with `normalize`.
|
|
63
|
+
- For a change users can see, add a changeset: run `pnpm changeset` at the
|
|
64
|
+
repository root. Start a breaking change's summary with `**Breaking:**`.
|
|
65
|
+
Do not edit `CHANGELOG.md` or `version` by hand; the release writes them.
|
|
66
|
+
See [packages/README.md](https://github.com/osdlc/osdlc/blob/main/packages/README.md).
|
package/LICENSE-APACHE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright 2026 Sizer LLC
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
package/LICENSE-MIT
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2026 sksizer
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|