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

Update the examples/-folder to account for outputting of JavaScript modules (PR 17055 follow-up) #17081

Merged
merged 3 commits into from
Oct 28, 2023

Conversation

Snuffleupagus
Copy link
Collaborator

This patch also changes most examples to use "top level await", since that's now supported and slightly simplifies the code.

… modules (PR 17055 follow-up)

This patch also changes most examples to use "top level await", since that's now supported and slightly simplifies the code.
 - Remove the `errorWrapper`-element, since it simplifies the example and is consistent with the default viewer; see PR 15533.

 - Simplify the l10n-handling, since the `NullL10n` should be able to translate everything e.g. without fallback values; see PR 17146.
…modules (PR 17055 follow-up)

*Please note:* While following the steps in the README still works with this patch, in the sense that the example runs and successfully renders a PDF document, I unfortunately cannot tell if it illustrates Webpack best practices.
@Snuffleupagus
Copy link
Collaborator Author

Snuffleupagus commented Oct 28, 2023

The only way to test this is locally, by running gulp dist-install and then checking that the various examples still work as before.
@timvandermeij Do you perhaps have time to review this?


Hopefully we should be getting pretty close to releasing version 4 now, however there's a couple of things that we should do first in my opinion:

  • Ensure that all release-blocker labeled stuff has landed. (There's also a few smaller Editor-related issues filed recently, e.g. this one, which if they're fixed soon would be nice to include.)
  • Given the amount of changes lately, allow a little time for things to settle to hopefully avoid unneeded breakage in the release.
  • Wait until more locales have been updated, since the Fluent migration-script wasn't able to convert all strings and they'll thus need to be manually translated (as part of the Firefox localization).

@timvandermeij
Copy link
Contributor

Yes, I agree it's a good idea to wait a bit longer with the final 4.0 release so we have enough time to finish up the last few issues/PRs and do more testing. I'll have a look at this PR soon.

Copy link
Contributor

@timvandermeij timvandermeij left a comment

Choose a reason for hiding this comment

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

Nice work; thanks!

@Snuffleupagus Snuffleupagus merged commit b798415 into mozilla:master Oct 28, 2023
3 checks passed
@Snuffleupagus Snuffleupagus deleted the examples-modules branch October 28, 2023 20:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
other release-blocker Blocker for the upcoming release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants