You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@legendecas can give more info, but it looks like Node.js is using //#sourceURL to map "virtual" files (created by transpiling TS on-the-fly) to their original filenames, without using a full source map. This is possible because in their implementation all the JS tokens are still in the original position, so mapping locations is not actually needed.
It does look to conflict a bit. I think we can loosen or remove the first link and have it not mention eval. I think it should just say we allow sourceUrl and it takes priority over source maps.
@legendecas can give more info, but it looks like Node.js is using
//#sourceURL
to map "virtual" files (created by transpiling TS on-the-fly) to their original filenames, without using a full source map. This is possible because in their implementation all the JS tokens are still in the original position, so mapping locations is not actually needed.Does our spec support this use case, or does it only support the comment in
eval()
? In https://tc39.es/source-map/#linking-evald-code-to-named-generated-code says that it's foreval()
'ed code, while in https://tc39.es/source-map/#linking-generated-code it also mentions it for "normal scripts".The text was updated successfully, but these errors were encountered: