resolve-pkglock 0.0.1

package/LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Axel Meinhardt
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,59 @@
+# resolve-pkglock
+
+Resolve your PNPM symlinks *without breaking builds* — use your `pnpm-lock.yaml` as the single source of truth for module resolution.
+
+`resolve-pkglock` hooks into Node.js’ modern [module customization hooks](https://nodejs.org/api/module.html#moduleregisterhooksoptions) to resolve your workspace dependencies directly from the PNPM store instead of through symlinks. This is especially useful in environments where symlinks cause issues (e.g. Docker, certain CI/CD setups, or read-only deployments).
+
+***
+
+## Why
+
+- **PNPM uses symlinks** in workspaces to deduplicate modules.
+- Some deployment environments **don’t preserve them**.
+- Luckily, everything needed for resolution is already in your **pnpm-lock.yaml**.
+
+By using `resolve-pkglock`, you can resolve dependencies directly from the PNPM store based on your lockfile — no symlinks required.
+
+***
+
+## Requirements
+
+- **Node.js v22.15.0** or newer (supports module hooks).
+- A **correctly maintained `pnpm-lock.yaml`** in your workspace root.
+
+***
+
+## Usage
+
+Load the module early in your entrypoint before other imports:
+
+```js
+// eslint-disable-next-line antfu/no-import-dist, antfu/no-import-node-modules-by-path
+import resolvePkgLock from './node_modules/.pnpm/resolve-pkglock.../node_modules/resolve-pkglock/dist/index.js';
+
+// Initialize with the path to your workspace root (where pnpm-lock.yaml lives)
+await resolvePkgLock(import.meta.dirname);
+
+// Then import your local packages normally
+import('your-local-package');
+```
+
+> ⚠️ Make sure you’re referencing the *non-symlinked folder* in the PNPM store when importing `resolve-pkglock`.
+
+***
+
+## Optional: Disable Symlinks Completely
+
+With `resolve-pkglock`, you can set this safely in your `pnpm-workspace.yaml`:
+
+```yaml
+symlink: false
+```
+
+This fully avoids the creation of symlinks while preserving the benefits of PNPM’s deterministic lockfile.
+
+***
+
+## License
+
+MIT © [ameinhardt](https://github.com/ameinhardt)

package/dist/index.d.ts

@@ -0,0 +1,2 @@
+declare function init(workspaceRoot: string): Promise<void>;
+export default init;