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.

Sign up for GitHub

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

Jump to bottom

Treat JS mapfile as an archive #3637

Open
pombredanne opened this issue Jan 11, 2024 · 0 comments · May be fixed by nexB/extractcode#58
Open

Treat JS mapfile as an archive #3637

pombredanne opened this issue Jan 11, 2024 · 0 comments · May be fixed by nexB/extractcode#58
Assignees
@keshav-space

Comments

@pombredanne
Copy link
Member

We could treat a JS mapfile as archive and extract its content as files under a <foo.mapfile-extract> directory. This would help with processing JS codebase in particular in ScanCode.io and PurlDB/MatchCode matching.
keshav-space added a commit to keshav-space/extractcode that referenced this issue Feb 1, 2024
@keshav-space
Support extraction of JavaScript map files
f5e39b8 
fixes nexB/scancode-toolkit#3637

Signed-off-by: Keshav Priyadarshi <git@keshav.space>
keshav-space added a commit to keshav-space/extractcode that referenced this issue Feb 1, 2024
@keshav-space
Support extraction of JavaScript map files
6d291a0 
fixes nexB/scancode-toolkit#3637

Signed-off-by: Keshav Priyadarshi <git@keshav.space>
@keshav-space keshav-space linked a pull request Feb 1, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@keshav-space keshav-space

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Support extraction of JavaScript mapfile keshav-space/extractcode
2 participants
@pombredanne @keshav-space