Patrick Kerschbaum

I guess this package `tiny-invariant` could just re-export the default function as a named export `assert`. So that people could do: ```ts import { assert } from 'tiny-invariant'; ``` Autosuggestion...

I made the code changes to export invariant as `assert` too here: https://github.com/alexreardon/tiny-invariant/compare/master...pkerschbaum:tiny-invariant:feat/export-as-assert. To determine the increase in size, I created the .tgz files which would get published to the...

No problem! Yes lets get back to it next year 👍

@alexreardon I was actually able to create a package [`@pkerschbaum/pkg-consumption-test`](https://www.npmjs.com/package/@pkerschbaum/pkg-consumption-test) which exposes a command to run the tests! Now the changes in this repository `tiny-invariant` are only the "package consumption...

I also updated the description of the PR.

I cannot reproduce this issue, see : ```txt ❯ npm run test $ node ./lib/test.js console.log after successful invariant usage! ``` Maybe some change since this issue was opened fixed...

Seems like I was able to apply a workaround for this problem: polyfilling `require` in ESM like this: ```mjs // File: "polyfill-require-in-esm.mjs" /** * This ESM module polyfills "require". *...

@zkochan oh right - when I set that setting to false by running `pnpm config --location=project set dedupe-peer-dependents=false`, the dependencies filter is applied again correctly! Consequently, this issue might have...

To create a pnpm patch for the changes `ts-patch` does, one can run these commands: ```bash pnpm patch [email protected] # [email protected]: pnpm --config.strict-peer-dependencies=false dlx [email protected] install --dir "/tmp/3c72b165312911e24b8745afb9b4b9eb" # or...

> > This would run ts-patch install as a postinstall script for typescript. > > Hi It does not seem to work fine @zkochan @ryoppippi this is not implemented yet,...