Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add an option to read sourcemap #5

Open
ooflorent opened this issue Sep 19, 2016 · 9 comments
Open

Add an option to read sourcemap #5

ooflorent opened this issue Sep 19, 2016 · 9 comments

Comments

@ooflorent
Copy link

Adding an option to access the source map would ease the integration with build tools.
e.g.:

const {code, map} = optimizeJs(input, {
  sourceMap: true,
  extractSourceMap: true,
})
@nolanlawson
Copy link
Owner

My bad, yes, this should be supported!

@sanex3339
Copy link

any news?

@matteoantoci
Copy link

+1, this is really important for vigneshshanmugam/optimize-js-plugin too. Thanks!

@sanex3339
Copy link

bump

@nicoecheza
Copy link

bump again

@ansballard
Copy link

Looks like this issue ties directly to #25, which seems to be stuck on implementation decisions.

Rough tl;dr: optimize-js uses https://www.npmjs.com/package/magic-string under the hood, but doesn't pass any options and only returns the parsed code. Looks like the current ideas are to return either a MagicString instance or a Map object, but that would definitely be a breaking change.

@jareguo
Copy link

jareguo commented May 4, 2017

bump

@pavelloz
Copy link

Nothing?

@ansballard
Copy link

#25 (comment)

Doesn't look like it's gonna happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants