More runtime compatibility
See original GitHub issuep-* function is useful, thank you for your great work.
Recently I had some trouble when I use them in some non node.js runtime, without bundler.
The error cause by:
p-* -> https://github.com/sindresorhus/aggregate-error -> https://github.com/sindresorhus/clean-stack/blob/main/index.js#L1
There is no os module in non node.js runtime.
So, it’s possible to stop using aggregate-error in p-*?
Issue Analytics
- State:
- Created 2 years ago
- Reactions:7
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Runtime Compatibility - Building Management WebHelp
Building Operation supports runtime compatibility between servers running two versions on a single system, during an upgrade process.
Read more >Version compatibility in .NET Framework - Microsoft Learn
To define the specific versions on which your app runs, add one or more <supportedRuntime> elements to your app's configuration file.
Read more >CUDA Compatibility :: NVIDIA Data Center GPU Driver ...
CUDA Compatibility document describes the use of new CUDA toolkit components on systems with older base installations.
Read more >Lambda runtimes - AWS Documentation
A runtime can support a single version of a language, multiple versions of a language, or multiple languages. Runtimes specific to a language...
Read more >Compatibility Guide for JDK 8 - Oracle
Behavioral: Behavioral compatibility includes the semantics of the code that is executed at runtime. For more information, see Kinds of Compatibility, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I too had to polyfill node
osto getp-allto work in browsers which seems a bit silly.Imho,
aggregate-errorshould drop its dependency onclean-stackas the stack cleaning performed there seems rather opinionated.This new
importsusage seems to break at least Jest (in ESM mode) which apparently does not support such resolution.