las-laz-js 0.1.0 → 0.3.0

package/CHANGELOG.md

@@ -1,5 +1,60 @@
 # Changelog
 
+## 0.3.0 (2026-10-21)
+
+Faster LAZ.
+
+- LAZ chunks decode in parallel on a pool of workers (browser Workers, Node worker_threads; one
+  fewer than the cores, at most 16), with the next window decoding while the current one becomes
+  columns. A 10-million-point LAZ reads in about 0.6 s (3.9 s on one thread); a 1.2 GB,
+  160-million-point LAZ in about 12 s (102 s in 0.2.0). Output is identical.
+- `openLas(src, { threads })`: automatic by default (used from 4 chunks up); `threads: 1` decodes
+  on the calling thread. Falls back to one thread when workers cannot start.
+- The decoder's hot loop does less: about 30% faster on one thread, same results.
+- Demo: decodes in the background with a progress bar, then shows the cloud once; colour, ramp
+  and range recolour the points already read instead of reading the file again.
+
+## 0.2.0 (2026-10-21)
+
+Reads LAZ.
+
+- LAZ (LASzip) point formats 0–3 and 6–8 (item versions 2 and 3; version 4 unchecked), with extra bytes, are read by `openLas` /
+  `readPoints` / `chunks` / `readPointsToScratch` and the worker exactly as LAS is: each chunk
+  is decompressed into plain LAS records, then decoded by the same code, so every option works
+  the same. Plain JavaScript, translated from laz-rs (Apache-2.0); the package licence is now
+  `MIT AND Apache-2.0` (see `NOTICE`).
+- Checked against an independent encoder: fixtures compressed by PDAL decode to exactly PDAL's own
+  decompression, and real files to exactly their LAS twins (1 M points), or to PDAL's decompression
+  (10 M points).
+- `reader.laz` describes the compression. Wave-packet LAZ items, LASzip item version 1 and files
+  without a chunk table are `UNSUPPORTED`; a LAZ cut short is `TRUNCATED`. `COMPRESSED_LAZ` is
+  no longer thrown.
+- Breaking: `strideFor` (deprecated in 0.1.1) is removed.
+- Demo: reads LAZ, and shows its compression.
+
+## 0.1.1 (2026-10-21)
+
+Fixes from the 0.1.0 review. No breaking changes.
+
+- `maxPoints` keeps exactly that many of the points that pass the filters, spread over the whole
+  file. It used to keep only the start of a file, and with filters set could return nothing.
+- Streamed chunks are coloured by one rule for the whole file, so windows no longer show seams
+  (new `createChunkColourizer`; `colourize` gains `eightBit`).
+- Opening a LAS 1.4 file no longer reads its EVLRs to the end of the file: a big EVLR has
+  `bytes: null` until `readEvlrBytes(i)`. VLRs and EVLRs report `length`.
+- Browser bundlers (esbuild, webpack, Vite) can bundle the package; the lazy Node import no
+  longer stops them.
+- `readPoints` and `writeLas` peak near the size of what they return (a 69 MB read peaked at
+  233 MB, now 74 MB); Node files are read into one reused window buffer.
+- `dedupe` is about 7 times faster.
+- `createLasWriter` works with OPFS scratch writers and Node file handles, and with
+  `writePoints` calls made without waiting.
+- A custom `{ size, read }` source that returns a short read is `TRUNCATED`, never fewer points.
+- Point formats 6–10 write their coordinate system as WKT, as LAS 1.4 requires; an EPSG code
+  alone is refused for them.
+- `strideFor` is deprecated (the reader no longer uses it) and goes in 0.2.0; `countKept` is new.
+- Demo: bounds, dedupe, colour range, return and intensity histograms; safe on big files.
+
 ## 0.1.0 (2026-10-21)
 
 First release: read and write ASPRS LAS.

package/LICENSE-APACHE

@@ -0,0 +1,51 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
+
+You must give any other recipients of the Work or Derivative Works a copy of this License; and
+You must cause any modified files to carry prominent notices stating that You changed the files; and
+You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
+If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
+
+You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
+5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS

package/NOTICE

@@ -0,0 +1,14 @@
+las-laz-js
+Copyright (c) 2026 Brent Buffham (https://kirra-design.com). MIT licence (see LICENSE).
+
+The LAZ decoder in src/laz/ is a JavaScript translation of laz-rs
+(https://github.com/laz-rs/laz-rs), which is itself a Rust port of LASzip
+(https://laszip.org) by rapidlasso. Those files are licensed under the
+Apache License, Version 2.0 (see LICENSE-APACHE), not the MIT licence:
+
+  (c) 2007-2015, martin isenburg, rapidlasso - fast tools to catch reality
+  (c) 2014, Uday Verma, Hobu, Inc.
+  (c) 2019-2023, Thomas Montaigu
+
+Changes: translated from Rust to JavaScript by Brent Buffham, 2026. Each
+translated file names the laz-rs source it came from in its header.

package/README.md

@@ -1,18 +1,22 @@
 # las-laz-js
 
-A JavaScript reader and writer for ASPRS **LAS** point clouds (LAZ to follow), published on npm
-as `las-laz-js`. Plain ES modules, no dependencies, runs in the browser and in Node — and built
-for files far larger than memory.
+A JavaScript reader and writer for ASPRS **LAS** point clouds, and a reader for **LAZ**
+(LASzip-compressed LAS), published on npm as `las-laz-js`. Plain ES modules, no dependencies,
+runs in the browser and in Node — and built for files far larger than memory.
 
 **Status: early (0.x).** It works and is tested, but the API may still change before 1.0.
 
 - Working: `openLas` reads the header, VLRs / EVLRs and coordinate system of LAS 1.0–1.4;
   `readPoints` and `chunks` decode every point format (0–10) a window at a time, with filters
   and thinning; `colourize` colours points; `writeLas` writes LAS 1.0–1.4.
-- Big files: a 1.1 GB, 34-million-point cloud reads in about 2 seconds in Node, and is never held
-  in memory whole.
-- Also: a ready-made module Worker (`las-laz-js/worker`) and a Three.js demo.
-- Not yet: reading LAZ (0.2.0) and writing LAZ (0.3.0).
+- LAZ: point formats 0–3 and 6–8, with extra bytes, read exactly like LAS — the same calls, the
+  same options, decoded chunk by chunk in plain JavaScript (no WebAssembly).
+- Big files: a 1.1 GB, 34-million-point LAS reads in under a second in Node, and a 10-million-point
+  LAZ decodes on every core (a 10-million-point file in about 0.6 s); neither is held in memory
+  whole (see LAZ below for the one exception).
+- Also: a ready-made module Worker (`las-laz-js/worker`) and a
+  [Three.js demo](https://brentbuffham.github.io/las-laz-js/).
+- Not yet: writing LAZ (0.3.0).
 
 ## Install
 
@@ -24,9 +28,14 @@ Node 22 or newer, or any current browser. No dependencies.
 
 ## Demo
 
-Drop a LAS file onto the page and it is read locally (never uploaded), in the library's Worker,
-and streamed into a Three.js viewer. The side panel runs every library function.
-Run it locally with `npm run demo`, then open http://localhost:8080/.
+Try it in the browser: **https://brentbuffham.github.io/las-laz-js/**
+
+Drop a LAS or LAZ file onto the page. It is read locally (never uploaded), decoded in the
+library's Worker (LAZ on every core) behind a progress bar, then shown once in a Three.js viewer;
+colour changes recolour the points already read, without reading the file again. The side panel shows the header, VLRs, coordinate
+system and LAZ compression; reads with class, return, bounds, thinning and dedupe filters;
+colours by RGB, intensity, elevation or class; lists point statistics; and saves the points back
+out as LAS. To run it locally: `npm run demo`, then open http://localhost:8080/.
 
 ## Reading
 
@@ -37,7 +46,10 @@ var las = await openLas(file);           // File / Blob, ArrayBuffer, Uint8Array
 las.header;   // { versionMajor, versionMinor, pointFormat, pointCount, bounds, scale, offset,
               //   software, systemId, creationDay, creationYear, pointsByReturn, compressed, ... }
 las.crs;      // { kind: "geokeys" | "wkt" | null, epsg, wkt?, keys? } — parsed, never reprojected
-las.vlrs;     // [{ userId, recordId, description, bytes }]
+las.vlrs;     // [{ userId, recordId, description, start, length, bytes }]
+las.evlrs;    // the same; an EVLR over 64 KiB (waveform data) has bytes: null until
+              //   await las.readEvlrBytes(i) — opening never reads it
+las.compressed; las.laz;   // true for LAZ; its compressor, chunk size and items (else null)
 
 var pts = await las.readPoints({
 	fields: ["x", "y", "z", "classification", "red", "green", "blue"],
@@ -60,12 +72,38 @@ red green blue nir`. Fields a point format does not hold are left out. `scanAngl
 degrees for every format.
 
 Filters run on the raw record before it is decoded, so a filtered-out point costs a byte read.
+`maxPoints` keeps exactly that many of the points that pass the filters, spread evenly over
+the whole file; with filters set it first counts the passing points, which reads the file twice.
+
+## LAZ
+
+A LAZ file is opened and read with the same calls as LAS. Each LASzip chunk (50,000 points in
+most files) is decompressed into the plain LAS records it holds, then decoded exactly as a LAS
+window is — so every option above works the same, and reading a LAZ gives the same columns as
+reading the LAS it was compressed from.
+
+- Read: point formats 0–3 (LASzip point-wise, item version 2) and 6–8 (layered, item version 3),
+  with extra bytes. Item version 4 follows laz-rs but has not been checked against a real file
+  (it differs from 3 only with several scanner channels).
+- Not read: wave-packet items (formats 4, 5, 9, 10 in LAZ), item version 1 (LASzip before 2011),
+  and files without a chunk table (an unfinished write). Each is refused with `UNSUPPORTED`,
+  naming what it found — never garbage points.
+- A LAZ file cut short is `TRUNCATED`.
+
+**Speed.** LAZ chunks are independent, so they are decoded on a pool of workers — browser
+`Worker`s or Node `worker_threads`, one fewer than the cores (at most 16) — while the next window
+is already decoding. A 10-million-point LAZ reads in about 0.6 s on a 24-core machine (about 4 s
+on one core). Files under four chunks (200,000 points) stay on one thread, where starting workers
+would cost more than it saves. `openLas(file, { threads: 1 })` decodes on the calling thread;
+`threads: n` asks for n workers. If workers cannot start, it falls back to one thread.
 
 ## Files bigger than memory
 
-`openLas` reads only the header and the VLRs. Points are read in windows of whole records
-(64 MiB by default, `openLas(file, { windowSize })`), so memory holds one window plus what you
-keep.
+`openLas` reads only the header and the VLRs. Points are read in windows (64 MiB of records by
+default, `openLas(file, { windowSize })`; for LAZ, whole chunks adding up to about that much
+decompressed), so memory holds one window plus what you keep. One exception: a LAZ written
+point-wise without chunks (LASzip before 2.0, rare) is one chunk, so its window is the whole
+decompressed file.
 
 ```js
 for await (var chunk of las.chunks({ fields: ["x", "y", "z"] })) {
@@ -87,23 +125,28 @@ Returns a `Uint8Array`, three bytes per point. LAS colour is 16-bit and is scale
 except in files that store 8-bit values in the 16-bit fields (a common writer bug), which are
 detected and used as they are instead of turning almost black. Elevation uses a blue → cyan →
 green → yellow → red ramp; intensity a greyscale over the 2nd–98th percentile; classification
-the usual LiDAR-viewer colours (ASPRS defines the codes, not colours).
+the usual LiDAR-viewer colours (ASPRS defines the codes, not colours). For streamed chunks,
+`createChunkColourizer` keeps one rule for the whole file, so windows match.
 
 ## Writing
 
 ```js
 import { writeLas, createLasWriter } from "las-laz-js";
 
-var bytes = await writeLas(pts, { version: "1.4", pointFormat: 7, crs: { epsg: 28350 } });
+var bytes = await writeLas(pts, { version: "1.2", pointFormat: 3, crs: { epsg: 28350 } });
+var v14 = await writeLas(pts, { version: "1.4", pointFormat: 7, crs: { wkt: las.crs.wkt } });
 
-var w = await createLasWriter(sink, { version: "1.2", pointFormat: 3, scale, offset });  // sink: { write(bytes, position) }
+var w = await createLasWriter(sink, { version: "1.2", pointFormat: 3, scale, offset });
+// sink: an OPFS writer from openScratchSyncWriter, a Node FileHandle, or any { write(bytes, position) }
 await w.writePoints(batch1); await w.writePoints(batch2);
 await w.close();   // patches the header totals
 ```
 
 A version and point format that do not go together (format 6 in LAS 1.2) are refused, never
 silently changed. Scale and offset are chosen from the bounds when not given. `crs.epsg`
-writes a GeoKey record; `crs.wkt` a WKT record.
+writes a GeoKey record; `crs.wkt` a WKT record. Point formats 6–10 must carry WKT (LAS 1.4), so
+an EPSG code alone is refused for them — the library has no projection database to turn a code
+into WKT. Writing LAZ arrives in 0.3.0.
 
 ## In a Worker
 
@@ -117,24 +160,33 @@ worker.postMessage({ id: 2, type: "chunks", payload: { fields: ["x", "y", "z"],
 The protocol is documented in `src/workers/workerProtocol.js` and can be driven directly with
 `createWorkerHandler(post)`.
 
+**Bundlers.** The worker entry and the LAZ decode workers are found through
+`new Worker(new URL(..., import.meta.url))`, which Vite and webpack 5 follow. With Vite, keep the
+package out of dependency pre-bundling (`optimizeDeps: { exclude: ["las-laz-js"] }`), so the
+worker files stay next to the module that loads them.
+
 ## Errors
 
 Every failure is a `LasError` with a stable `code` (`ERROR_CODES`) and, for byte-level problems,
-the file `offset`: `NOT_LAS`, `UNSUPPORTED_VERSION`, `UNSUPPORTED`, `COMPRESSED_LAZ`,
-`TRUNCATED`, `BAD_HEADER`, `BAD_VLR`, `INVALID_ARGUMENT`, `ABORTED`, `TOO_MANY_POINTS`.
-A file shorter than its header promises is `TRUNCATED`, never garbage points.
+the file `offset`: `NOT_LAS`, `UNSUPPORTED_VERSION`, `UNSUPPORTED`, `TRUNCATED`, `BAD_HEADER`,
+`BAD_VLR`, `INVALID_ARGUMENT`, `ABORTED`, `TOO_MANY_POINTS`. A file shorter than its header
+promises is `TRUNCATED`, never garbage points. (`COMPRESSED_LAZ` is kept for 0.1 callers but is no
+longer thrown: LAZ is read.)
 
 ## Scope
 
 Reprojection is out of scope (the coordinate system is reported, not changed). Waveform
-formats 4, 5, 9 and 10 have their point fields read; the waveform data itself is not. COPC,
-EPT and E57 are not read.
+formats 4, 5, 9 and 10 have their point fields read from LAS; the waveform data itself is not.
+COPC, EPT and E57 are not read.
 
 ## Provenance
 
 The LAS reader, writer and big-file handling come from [Kirra](https://kirra-design.com),
-Brent Buffham's blast-design app, rewritten as a standalone library. The LAZ codec (0.2.0) is
-being ported from [laz-rs](https://github.com/laz-rs/laz-rs), used under its MIT licence.
+Brent Buffham's blast-design app, rewritten as a standalone library. The LAZ decoder in
+`src/laz/` is a JavaScript translation of [laz-rs](https://github.com/laz-rs/laz-rs) by Thomas
+Montaigu, itself a Rust port of [LASzip](https://laszip.org) by Martin Isenburg (rapidlasso).
+It is checked against an independent encoder: the test fixtures were compressed by
+[PDAL](https://pdal.io), and every record must equal PDAL's own decompression.
 Formats are written to the ASPRS LAS 1.4 R15 specification; see `docs/LAS_FORMAT_NOTES.md`.
 
 ## Development
@@ -144,11 +196,16 @@ npm test               # node --test, every test
 npm run test:coverage  # with the coverage gate
 npm run demo           # the demo on http://localhost:8080/
 npm run check:private  # before every push: no private sample details in the repo
+node _dev/makeLazFixtures.mjs   # remake test/fixtures/laz with PDAL (needs PDAL 2.x)
 ```
 
 Private sample files go in the gitignored `samples/` folder, or are listed by path in
-`samples/paths.txt`; the sample tests compare each file with its own header.
+`samples/paths.txt`; the sample tests compare each file with its own header, and each LAZ with a
+LAS twin (same count and bounds) field by field.
 
 ## Licence
 
-MIT © Brent Buffham
+`MIT AND Apache-2.0`. The library is MIT © Brent Buffham (`LICENSE`). The LAZ decoder in
+`src/laz/`, translated from laz-rs / LASzip, is under the Apache License 2.0 (`LICENSE-APACHE`,
+`NOTICE`). Both are permissive: use, change and ship it in open or closed software, keeping the
+notices.

package/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "las-laz-js",
-	"version": "0.1.0",
-	"description": "Zero-dependency JavaScript reader and writer for ASPRS LAS point clouds (LAZ to follow), for the browser and Node, built for files larger than memory.",
+	"version": "0.3.0",
+	"description": "Zero-dependency JavaScript reader and writer for ASPRS LAS point clouds, and reader for LAZ (LASzip), for the browser and Node, built for files larger than memory.",
 	"type": "module",
 	"exports": {
 		".": "./src/index.js",
@@ -11,6 +11,8 @@
 		"src",
 		"README.md",
 		"LICENSE",
+		"LICENSE-APACHE",
+		"NOTICE",
 		"CHANGELOG.md"
 	],
 	"sideEffects": false,
@@ -36,7 +38,7 @@
 		"threejs"
 	],
 	"author": "Brent Buffham (https://kirra-design.com)",
-	"license": "MIT",
+	"license": "MIT AND Apache-2.0",
 	"repository": {
 		"type": "git",
 		"url": "git+https://github.com/brentbuffham/las-laz-js.git"