Sindre Sorhus

Closing as it's not worth the risk.

You need to open an issue on the TypeScript repo about this. This package is defined correctly. The problem is that `moduleResolution: bundler` assumes not `node`, so they need to...

I would prefer not to. If all packages just work around the problem, the TypeScript team has no incentive to prioritize fixing this.

This is an extreme edge-case, but a good pull request with tests would be accepted.

Thinking about this more, I think this is out of scope. The module intentionally returns undefined when node_modules isn’t writable to keep the behavior simple and predictable. Use the documented...

Most likely a SwiftUI bug. The issue was introduced by https://github.com/sindresorhus/Defaults/commit/2dad0e446e0b2acffbe65846030ec2de81995061, but that was done to work around another SwiftUI bug, so we cannot just revert that.

I haven't looked into yet, and I don't plan to until I know whether macOS 16 (or 26) fixes it.

This would be super useful 👍 --- Some inspiration: - https://github.com/SwiftyLab/MetaCodable - https://github.com/mikhailmaslo/macro-codable-kit - https://github.com/WendellXY/CodableKit

> Any idea why when I ran this with the macos-14 image I got errors for missing properties. They are marked with if #avalable(macOS 15) 🤔 Using new properties only...

> For now, kept the other as the default, since the add-on can't be cross-platform compiled until this is released The goal should be to only have the native add-on....