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

Enables source maps for webpack generated files. #8368

Merged
merged 2 commits into from
May 5, 2017

Conversation

yurydelendik
Copy link
Contributor

@yurydelendik yurydelendik commented May 3, 2017

screen shot 2017-05-03 at 12 40 05 pm

@yurydelendik
Copy link
Contributor Author

/botio-windows preview

@pdfjsbot
Copy link

pdfjsbot commented May 3, 2017

From: Bot.io (Windows)


Received

Command cmd_preview from @yurydelendik received. Current queue size: 0

Live output at: http://54.215.176.217:8877/4772af15ba20521/output.txt

@pdfjsbot
Copy link

pdfjsbot commented May 3, 2017

From: Bot.io (Windows)


Success

Full output at http://54.215.176.217:8877/4772af15ba20521/output.txt

Total script time: 19.73 mins

Published

Copy link
Collaborator

@Snuffleupagus Snuffleupagus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While this seem to work just fine in my testing, I've got a couple of questions:

  • First of all, the generated .map files seem to be approximately two times larger than their corresponding .js files. Am I missing something here, or are they supposed to be that big?
    Are there any settings to compact them somewhat? For example, there seem to be a lot of (unnecessary?) white-space in the .map files.
  • Second of all, the .map files are being bundled into the output of all of the built targets by defaults.
    For e.g. the FIREFOX/MOZCENTRAL builds[1], I'm assuming that may not be what we want (at least not right now), given the point above regarding the size of the .map files?

[1] I recall that there was some initial resistance about file sizes when the Adobe CMaps where originally added. However, they were less than 1 MB, so I'd assume that people would really object if the size of the pdfjs directory in mozilla-central went from 3 to 6 MB overnight :-)

@yurydelendik
Copy link
Contributor Author

First of all, the generated .map files seem to be approximately two times larger than their corresponding .js files.

It's expected. I also configured map to include original files content, so we don't have to ship ton of separate files.

Second of all, the .map files are being bundled into the output of all of the built targets by defaults. For e.g. the FIREFOX/MOZCENTRAL builds...

Yes, now I think, we need to disable maps for FIREFOX/MOZCENTRAL/CHROME

@yurydelendik
Copy link
Contributor Author

/botio-windows preview

@pdfjsbot
Copy link

pdfjsbot commented May 5, 2017

From: Bot.io (Windows)


Received

Command cmd_preview from @yurydelendik received. Current queue size: 0

Live output at: http://54.215.176.217:8877/5fcf5142fe01f77/output.txt

@pdfjsbot
Copy link

pdfjsbot commented May 5, 2017

From: Bot.io (Windows)


Success

Full output at http://54.215.176.217:8877/5fcf5142fe01f77/output.txt

Total script time: 20.19 mins

Published

Copy link
Collaborator

@Snuffleupagus Snuffleupagus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for answering my questions, that helped to clear things up!

With this now being excluded from the extensions, I don't have any reservations.
r=me, since this works just fine; thank you!

@yurydelendik yurydelendik merged commit deae2d8 into mozilla:master May 5, 2017
@yurydelendik yurydelendik deleted the sourcemap branch May 5, 2017 14:32
movsb pushed a commit to movsb/pdf.js that referenced this pull request Jul 14, 2018
Enables source maps for webpack generated files.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants