javascript-obfuscator / javascript-obfuscator/webpack-obfuscator

Unobfuscated sourcemaps?

Open
#97 2 comments 8 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
928
Forks
92
PR merge metrics
No merged PRs in 30d

Description

Wondering if it's possible to have sourcemaps unobuscated?

Currently uploading the sourcemaps to Sentry and although it finds where the exception occurred in, the contents are mainly obfuscated. This is the output I get:

![h](https://pouch.jumpshare.com/preview/f3ZGKpuJp98mM8WWrpjq3lrUcU8QJ9ztBOoppm06taYWAwL8J66gn3bA702I6btzkiRmVG6jeLe7iN3cd0gxmDJprjKJn4snkOQIlHyX-Do)

Contributor guide

No contributing guide indexed for this repository

Research direction

Review the webpack-obfuscator sourcemap generation path and compare the reported Sentry output with the desired unobfuscated contents. Determine whether the plugin can expose an option or change its sourcemap behavior; done means documenting or implementing a clear way to obtain usable, unobfuscated sourcemaps.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, webpack
Domain
build-system
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.