enquirer
deno-puppeteer
Our great sponsors
enquirer | deno-puppeteer | |
---|---|---|
18 | 5 | |
7,468 | 441 | |
0.5% | - | |
4.9 | 0.0 | |
3 days ago | 4 months ago | |
JavaScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
enquirer
-
For achieving the widest adoption among Windows users, which commonly used scripting language would be best suited for a CLI program?%
Although I'm happy there is a way to bundle Node.js apps with support for pnpm, and for a modern-ish version of Node.js, it's somewhat slow in my experience to build locally. Interactivity doesn't have the greatest ecosystem there, especially with TypeScript. Best library I've found is Enquirer.
-
💡 Generate package.json From GitHub
{ "name": "@jonschlinkert/omit-deep", "description": "Recursively omit specified keys from an object", "tags": ["object", "deep", "remove", "omit"], "version": "0.3.0", "author": "Jon Schlinkert (https://github.com/jonschlinkert)", "repository": "jonschlinkert/omit-deep", "bugs": "https://github.com/jonschlinkert/omit-deep/issues", "license": "MIT" }
-
Using generators to improve developer productivity
In case you need to ask for user input, optionally you can use a prompt file. This is very useful to customize the output of the generator. Prompts are defined using a library named Enquirer.
-
NPM Vulnerability Discussion on Twitter
> I don't fully understand why packages like this are so popular.
It actually works like this: Author X develops `iseven`, `isodd`, etc. No one really downloads such packages. Author X then develops `importantPackage` which does do something useful developers out here download. Now `iseven`, `isodd` are downloaded alongside `importantPackage`.
My point is, we should recognize certain NPM authors as toxic, but I guess "freedom of speech/code" stops us from doing so. Example of such an author: https://github.com/jonschlinkert/
-
Call for Deno module ideas
something like enquirer
-
I will pay you cash to delete your npm module
You're thinking of Jon Schlinkert, publisher of 1435 packages on npm.
-
NPM – is-even, 160k weekly downloads
https://github.com/jonschlinkert
Interesting, 845 repositories by the user, and the vast majority of them are simple NPM modules such as this one.
Has there been any recent instances of someone abusing simple NPM repos like this for malicious intent?
> From the github user's ("i-voted-for-trump") bio:
> EDIT - read some of the comments and there is some anger and confusion. Folks, this is a troll. Yes, npm and the JS ecosystem have some flaws, but let's not get bent out of shape.
It doesn't look like so. The author is definitely creating some confusion, but the readme of his professional Github's account (https://github.com/jonschlinkert) says:
> Several years ago I switched careers from sales, marketing and consulting to learn how to program, with the goal of making the world a better place through code. [...] To date, I've created more than 1,000 open source projects in an effort to reach my goal. Open source software takes a lot of time to create and maintain. You can help me to achieve my goals of changing the world through code, help me create better developer experiences, or just say thank you by sponsoring me on GitHub.
He's asking for real money; he's definitely not a troll.
He probably moved that repo away from his profile (https://github.com/jonschlinkert) to avoid being trolled
It's insanely funny to me that these packages exist while one of his bigger projects (https://github.com/enquirer/enquirer) lists the following reason under "why use it":
> Lightweight - Only one dependency, the excellent ansi-colors by Brian Woodward.
deno-puppeteer
-
Unity ships Node-IPC vulnerability
In an ideal world, yes, but in reality Deno's permission model is quite hard to use so many libraries require disabling a lot of it, sometimes everything like puppeteer. Other example is the library I maintain: it requires --allow-net since you can't whitelist a domain and all its subdomains, just a domain.
-
What's the best way to generate a PDF from html in deno?
https://github.com/lucacasonato/deno-puppetee
import puppeteer from "https://deno.land/x/[email protected]/mod.ts"; const browser = await puppeteer.launch(); const page = await browser.newPage(); await page.goto("https://news.ycombinator.com", { waitUntil: "networkidle2", }); await page.pdf({ path: "hn.pdf", format: "A4" }); await browser.close();
-
BREAKING!! NPM package ‘ua-parser-js’ with more than 7M weekly download is compromised
Maybe people forget about this permission system because either are not experienced with Deno or because they just slap -A on eveything. Some packages such as deno-puppeteer even put it in all examples without even adding a note about its risks.
What are some alternatives?
prompts - ❯ Lightweight, beautiful and user-friendly interactive prompts
puppeteer-cluster - Puppeteer Pool, run a cluster of instances in parallel
puppeteer - Node.js API for Chrome
oclif - CLI for generating, building, and releasing oclif CLIs. Built by Salesforce.
jsPDF - Client-side JavaScript PDF generation for everyone.
react-pdf - 📄 Create PDF files using React
handlebars-helpers - 188 handlebars helpers in ~20 categories. Can be used with Assemble, Ghost, YUI, express.js etc.
deno - A modern runtime for JavaScript and TypeScript.
terminalizer - 🦄 Record your terminal and generate animated gif images or share a web player
ua-parser-js - UAParser.js - Free & open-source JavaScript library to detect user's Browser, Engine, OS, CPU, and Device type/model. Runs either in browser (client-side) or node.js (server-side).
npm-force-resolutions - Force npm to install a specific transitive dependency version
cli - the package manager for JavaScript