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
Thanks for posting this @basarat. I have a question: is the fact this package does not include source map files (.js.map) is intentional? I'm trying to make a similar decision for a much larger package a TypeScript port of the ANTLR4 runtime.
Clearly source maps are not required for runtime use, but then again, neither are the original TypeScript sources. It seems like if we include the .ts sources in the NPM package, having the .js.map is a natural accompaniment.
The text was updated successfully, but these errors were encountered:
Thanks for posting this @basarat. I have a question: is the fact this package does not include source map files (
.js.map
) is intentional? I'm trying to make a similar decision for a much larger package a TypeScript port of the ANTLR4 runtime.Clearly source maps are not required for runtime use, but then again, neither are the original TypeScript sources. It seems like if we include the
.ts
sources in the NPM package, having the.js.map
is a natural accompaniment.The text was updated successfully, but these errors were encountered: