Skip to content
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.

rename? #28

Open
holic opened this issue Jun 26, 2022 · 12 comments
Open

rename? #28

holic opened this issue Jun 26, 2022 · 12 comments

Comments

@holic
Copy link
Owner

holic commented Jun 26, 2022

It was web3-dapp-scaffold, then web3-app-scaffold (because I didn't feel right calling it a decentralized app), and now web3-scaffold.

I'm not a massive fan of the "scaffold" word, feels a little obscure, borrowed from Ruby(?), and probably hurts word of mouth long term?

Maybe create-web3-app?

@davisshaver
Copy link
Contributor

I see your points about scaffold, although I happen to like it as a name. I also like the idea of create-web3-app although my expectation for create-* projects is that there's a CLI interface to get started. Maybe this is the direction you want to head? In terms of other synonyms for scaffold, I think "starter" or "starter kit" is a common one. Curious to hear what others think about this too.

@jamiew
Copy link
Contributor

jamiew commented Jun 28, 2022

I had the same thought re. create-* pattern -- arguably we could add the CLI bits? Is that worth the work?

I have no qualms with web3-scaffold too, which is self-descriptive. I also miss ruby though

@holic
Copy link
Owner Author

holic commented Jun 29, 2022

Yeah, my thought with create-web3-app was that it'd be neat to have support for npm init web3-app (and potentially other CLI options). Could potentially make it pluggable, e.g. make Tailwind optional.

Looks like someone snagged this name a few years back though: https://www.npmjs.com/package/create-web3-app

@holic
Copy link
Owner Author

holic commented Jun 29, 2022

Also just came across https://www.npmjs.com/package/create-web3, which lets you pick Next/Vite, Hardhat/Foundry, etc. Pretty neat!

@davisshaver
Copy link
Contributor

+1 to all of this. A CLI interface would be very cool at some point.

I wonder if there's an architecture that would let us keep this repo (maybe converting to a template repo at some point?) and build a CLI helper at a future date which wraps the repo and makes it easy to customize things.

@holic
Copy link
Owner Author

holic commented Jun 29, 2022

maybe converting to a template repo at some point?

Fun fact: this was a template repo! but github nukes commit history and it was hard to port changes over, so I moved it back to a regular repo that you'd fork

@e-roy
Copy link

e-roy commented Jun 30, 2022

first thing I think of when I hear scaffold is scaffold-eth. not suggesting a change in name, just saying it does resonate in the web3 space

@jamiew
Copy link
Contributor

jamiew commented Jun 30, 2022

eyyy a wild create-web3 author appears :) welcome @e-roy

@holic
Copy link
Owner Author

holic commented Jul 4, 2022

Chatted with the previous owner of create-web3-app and he generously handed over the name! https://www.npmjs.com/package/create-web3-app

@jamiew
Copy link
Contributor

jamiew commented Jul 5, 2022 via email

@cjpais
Copy link

cjpais commented Jul 6, 2022

+1 to all of this. A CLI interface would be very cool at some point.

I wonder if there's an architecture that would let us keep this repo (maybe converting to a template repo at some point?) and build a CLI helper at a future date which wraps the repo and makes it easy to customize things.

I might have created an issue for this accidentally, hadn't read this thread yet

#40

@samkingco
Copy link

Yeah I’d also love a CLI, even if it just copies the template, inits a new git repo, and renames all the packages to my project name. I thought about putting one together next week. Should be quite straightforward.

Right now I have to fork/clone the repo and then nuke history and do a bunch of find and replace. Having one command would be great, and the create-web3-app fits that mental model better.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants