-
-
Notifications
You must be signed in to change notification settings - Fork 141
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
v2.0.0 release #55
v2.0.0 release #55
Conversation
Due to issues on systems with ownership problems of the module, avoided saving a file in module folder #52
Switched over using puppeteer-core to avoid chromium download on every install. With chrome-launcher, lib will first try to locate any Chromium instance that is installed on users system, and only if not found, it will installed preferred chromium revision that is declared on puppeteer-core pkg. fix #50
Added error handling for chrome-launcher fix #50
Alignment with pptr install script
Added a manual chromium installation step for testing
Added async chrome process cleanup
Added single quotes option for generated HTML tags fix #49
Added an option to generate favicon images and associated meta fix #47
Added puppeteer-core feature details to docs fix #50
Generate iOS splash screen meta with (prefers-color-scheme: dark) media attr [default: false] BREAKING CHANGE: generateImages method from the module API now returns HTMLMeta object with the chunks of HTML content, instead of one big HTML string fix #51
Added a global configuration file jest.setup.js for jest timeout configuration
Better handling of initialization and killing of the browsers for both scenarios of using system browser and package chromium re #50
Suppressed security warning for now by changing package versioning strategy fix #53
@@ -98,8 +85,6 @@ test('generates icons and splash screens when both only flags exist', async () = | |||
}); | |||
|
|||
test('generates icons and splash screens with path prefix', async () => { | |||
jest.setTimeout(TEST_TIMEOUT_IN_MILLIS); | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔥
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work bro!
.reduce( | ||
(acc, promise: Promise<SavedImage>) => | ||
acc.then(result => promise.then(Array.prototype.concat.bind(result))), | ||
Promise.resolve([] as SavedImage[]), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hardcore Promise.all
:)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
More like promise.map or promise.each bro, instead of running all instances in parallel, it executes and kills one by one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well done, bro!
🎉 This PR is included in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
fixes #47
fixes #49
fixes #50
fixes #51
fixes #52
fixes #53
Sorry for relatively large review. I hope you can reserve some time for it asap.