Aleksander Heintz

> Then it would have an actual use case I'm sorry. Have you met functional programming before? Not to mention that even with this not being accepted in forever, there...

Oh, and I'd just like to add that using ThreadStatic values/properties (HttpContext.Current) in a async context sounds risky at best, though I'm also guessing that the CLR team has thought...

I would personally very much like something like an `forcePnpmWorkspacePackagesWildcard` (maybe less wordy) that makes sure all packages that are versioned `workspace:` get's turned into `workspace:*`. All of them being...

Just encountered this issue with a slightly different setup. I have the following in my `exports`: ```json "exports": { ".": { "import": "./dist/index.js" }, "./runtime.js": { "import": "./dist/runtime.mjs" } },...

In case someone else arrives here with this issue before it's solved, and need a work-around, I ended up just using a non-aliased file-extension in my `exports`: ```js "exports": {...

@alexander-akait it was not a "don't use it cause it's unsafe". It was just a general in my honest opinion, it's a bad idea to use `*` exports, cause you...

Ah, right, I didn't notice that my computer changed line-endings. Will resolve that. The only things I changed in TestRequest was uncomment the "safari" request. I also agree with separating...

There you go. Nice and clean commits.

After reading through most of your feature-list on http://james.newtonking.com/json, it would seem that a lot of the requested features are already present in `Newtonsoft.Json`. What you already support are (according...

You should definitely expect changes in the serialized bytes between different major versions I would think. Pre 1.0.0, I would also assume breaking changes in minor versions. Note; I'm not...