Andrew Bradley
Andrew Bradley
Is there a minimal example of the .js file raising this error?
It can be a new one, just needs to be an example that can be used to test with. Requesting a minimal reproducible example is common practice in open-source: https://en.wikipedia.org/wiki/Minimal_reproducible_example
We discussed this on Discord: https://discord.com/channels/508357248330760243/508357707602853888/843546169752813589 ### Conclusions: * Use node's warnings API: `process.emitWarning()` * there is already precedent for warnings to emit to stderr from here * node already...
Looks like the schema-based tooltips could be generated using https://github.com/microsoft/vscode-json-languageservice If that seems like an interesting idea, I can extract it to a separate issue.
@TimoRoth for what it's worth, we ended up going with CodeCov because it fit our use-case better. We were seeing some confusing behavior from coveralls -- reporting coverage decreased /...
This is also causing TypeStrong/ts-node#1790 The sourcemap spec says that `sourceRoot` / `sources` can be / should be file URIs. https://sourcemaps.info/spec.html > ### Resolving Sources > If the sources are...
For the istanbul maintainers, I think this issue can be renamed into a bug report: istanbul does not handle spec-compliant sourcemaps with file:// URI sources / sourceRoot The bugfix is...
I'm not trying to stir up trouble. However, I think it's fair to say that istanbul intends to support sourcemaps in whatever spec-compliant form they may take, since they might...
As far as I can tell, the PR to fix this will be small. For potential implementers: These two functions need to understand when they've received a file URI. https://github.com/istanbuljs/istanbuljs/blob/master/packages/istanbul-lib-source-maps/lib/pathutils.js...
@WrathChaos My guess is it depends on node's built-in `util` library, so it is not intended for use in React Native. If React Native doesn't have an implementation of node's...