fix: skip unknown chunk types instead of aborting the whole read

[mpicciolli]

Summary

• readChunk() threw immediately on any chunk type it didn't recognize, which would make the library entirely unable to parse a save file the moment a future game version introduces a new chunk type — even if that chunk is unrelated to the tables/data actually being read.
• Since every chunk header already carries its own chunkSize, an unknown chunk can now be skipped by byte count (logging a console.warn) instead of aborting the whole parse.
• Given the project already supports save formats spanning 2014–2025, forward compatibility with future chunk types seems like a reasonable goal.

[Copilot]

Pull request overview

This PR improves forward compatibility in the CDB binary reader by no longer aborting parsing when it encounters an unknown chunk type, allowing newer game versions to introduce additional chunks without breaking table/data extraction.

Changes:

• Replace the hard error on unknown chunk types with logic that skips over the chunk using the declared chunkSize.
• Emit a warning when an unknown chunk is encountered (currently via console.warn).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

Comments suppressed due to low confidence (1)

src/reader.ts:256

• The unknown-chunk path logs "Skipping..." before validating the declared chunk size, which can produce a misleading warning immediately before throwing. Also, checking typeof console !== "undefined" doesn’t guarantee console.warn exists.

					if (typeof console !== "undefined") {
						console.warn(
							`Skipping unknown chunk type: 0x${(header.chunkType as number).toString(16)} at position ${chunkStartPos}`,
						);
					}

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

src/reader.ts:256

• console.warn(...) is called unconditionally once console exists. In some JS runtimes console may exist but console.warn may be missing/non-function (or stubbed), which would throw while trying to recover from an unknown chunk. Consider using a safe optional invocation via globalThis.console?.warn?.(...) so skipping remains non-fatal across environments.

					if (typeof console !== "undefined") {
						console.warn(
							`Skipping unknown chunk type: 0x${(header.chunkType as number).toString(16)} at position ${chunkStartPos}`,
						);
					}