Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Plasmo – a framework for building modern Chrome extensions

github.com

Post reply on HN
Print view View original

21–30 of 39 posts

Re: Show HN: Plasmo – a framework for building modern Chrome extensions

#22

Post by httgp »

cxr wrote: post #18
coldsauce wrote: post #14

Earlier quoted context omitted.

Our tooling is written in Node.js. So developers must have Node installed on their machines to utilize our tooling. When they use our CLI to watch the file system for changes for live-reload or to build their extension, etc., that's a Node.js program. The build target is browser Javascript, though.

> Our tooling is written in Node.js. Sure. My question is why.

Why not?

Re: Show HN: Plasmo – a framework for building modern Chrome extensions

#23

Post by ghotli »

cxr wrote: post #18
coldsauce wrote: post #14

Earlier quoted context omitted.

Our tooling is written in Node.js. So developers must have Node installed on their machines to utilize our tooling. When they use our CLI to watch the file system for changes for live-reload or to build their extension, etc., that's a Node.js program. The build target is browser Javascript, though.

> Our tooling is written in Node.js. Sure. My question is why.

Surely you are trolling? That's a very, very common setup. Nothing complicated or out of the ordinary requiring specific tooling for the dev environment.

The output that runs in the browser at runtime has its own set of same constraints. Modern browser version, etc.

Re: Show HN: Plasmo – a framework for building modern Chrome extensions

#25

Post by quickthrower2 »

silax wrote: post #10

Love this. Chrome extensions are the most underrated platform to spit out 7+ figure recurring revenue businesses on. Mac App Store close second. I'm hesitant to even mention because it's such a good secret.

So are you saying P(success|browser extension) > P(success|web app)?

All other things being equal.

Re: Show HN: Plasmo – a framework for building modern Chrome extensions

#27

Post by cuylerstuwe »

ekabod wrote: post #13
silax wrote: post #10

Love this. Chrome extensions are the most underrated platform to spit out 7+ figure recurring revenue businesses on. Mac App Store close second. I'm hesitant to even mention because it's such a good secret.

Can you point to one extension that is making 7 figures?

Are you looking very specifically for “ONLY 7 figures”?

Revenue, or profit?

Not hard to think of a handful of big players in revenue; 1Password and Honey spring instantly to mind as 9-figure revenue players.

Re: Show HN: Plasmo – a framework for building modern Chrome extensions

#28

Post by cuylerstuwe »

cxr wrote: post #18
coldsauce wrote: post #14

Earlier quoted context omitted.

Our tooling is written in Node.js. So developers must have Node installed on their machines to utilize our tooling. When they use our CLI to watch the file system for changes for live-reload or to build their extension, etc., that's a Node.js program. The build target is browser Javascript, though.

> Our tooling is written in Node.js. Sure. My question is why.

It’s a norm for frontend devs to build CLI tools in the language/evironments/ecosystems they’re most familiar with.
Post reply on HN