html-to-image-puppeteer
Advanced tools
Node.js library to convert HTML to image using Puppeteer.
To install the dependencies, run:
npm install
Usage
Here is an example of how to use the library:
const { convertHtmlToImage } = require('html-to-image-puppeteer');
const htmlContent = '<html><body><h1>Hello, World!</h1></body></html>';
const outputPath = 'output.png';
convertHtmlToImage(htmlContent, outputPath)
.then(() => {
console.log('Image created successfully!');
})
.catch((error) => {
console.error('Error creating image:', error);
});
Scripts
test: Run the tests using Jest.
lint: Lint the code using ESLint.
build: Compile the TypeScript code to JavaScript.
To run a script, use:
For example, to run the tests:
Contributing
Contributions are welcome! Please open an issue or submit a pull request.
Contributors
Subodha Sahu (subodha.sahu-graymatter@monotype.com)
License
This project is licensed under the MIT License. See the LICENSE file for details.
FAQs
Node.js library to convert HTML to image using puppeteer
The npm package html-to-image-puppeteer receives a total of 0 weekly downloads. As such, html-to-image-puppeteer popularity was classified as not popular.
We found that html-to-image-puppeteer demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.