search

ahmadawais / create-guten-block

📦 A zero-configuration #0CJS developer toolkit for building WordPress Gutenberg block plugins.
https://Awais.dev/cgb-post
MIT License
3.15k stars 328 forks source link

Consider officially deprecating CGB #298

Open richtabor opened 3 years ago

richtabor commented 3 years ago

First off, super props for jumping on the need that CGB solved back in the day @ahmadawais. There didn't exist an easy way to spin up Gutenberg blocks and CGB certainly filled that gap. You've helped a lot of folks jump into Gutenberg/JS (including myself).

I do question though, now that WordPress has an official @wordpress/create-block package for scaffolding blocks, should CGB be officially deprecated?

A few reasons to consider this:

  1. There hasn't been activity here in about a year, while the @wordpress/create-block package is maintaining pace quite well with Gutenberg/the WordPress Block Directory requirements.
  2. Folks diving into Gutenberg block development that start with CGB will learn outdated methods for registering/building blocks, some of which are incompatible with the WordPress Block Directory.
  3. The WPCLI scaffolding command has been deprecated in support of @wordpress/create-block.
  4. @wordpress/create-block really is a great, highly supported, tool for scaffolding blocks.

If you feel this is an appropriate course of action, let's update the readme with a deprecation warning - similar to what WP-CLI has done. I'd be happy to submit a PR for this.

Thanks!

bahia0019 commented 2 years ago

I'll second this. I started a project last year with CGB, and starting back up on it. I didn't even know about the official WP starter block! I came here looking for a solution to import { withState } from '@wordpress/compose', and found this post.

If there are new tools available, and currently being developed, it'd be helpful to know.

Thank you for all you've done @ahmadawais!

ahmadawais commented 2 years ago

Thanks for the comments y'all. In the long run, this project became something I couldn't support all by myself for free. However, I wanted to find a couple of great developers who'd keep it up to date — I know @asharirfan was looking at this at some point.

With not enough support both from the development and monetary perspective, this project has suffered staleness in the last year or so.

I agree we should be using the latest, most up-to-date tool out there, which seems to be the one being maintained by the WP repo, that took what we started here (zero-config tooling) and moved it forward. Which I'm always excited about.

I'm okay with you sending a PR for depreciation, and I'd also still like to see this project revived as a community project which can always move faster than the official projects and help people innovate.

Interested folks can reach out to me at https://Awais.dev/dm on Twitter or send me an email.

Peace! ✌️

althe3rd commented 2 years ago

So I am certainly not a gutenberg expert here but upon trying to use @wordpress/create-block I found it to be lacking in many ways. I imagine there are ways to address these shortcomings but I couldn't figure out how to package multiple blocks in a single instance of create-block even though that's easy and well supported in create-guten-block.

All of this is another way of saying that I wouldn't want create-guten-block to go away until @wordpress/create-block was actually up to par with what create-guten-block has.

Brandoning commented 2 years ago

Please deprecate this.

Good idea in theory but the number of outdated packages and lack of maintenance means that it has been more of a pain to use than the time it should have saved, more recently.

If you do update the packages half of them fail heavily and need modifications to the scripts to get them working again (Ora, Webpack, ExtractTextPlugin is now deprecated but it's still used here).

mikemanger commented 2 years ago

I'll join everyone by saying thanks for the project, we adopted it early and have many projects using it.

I'm looking to remove this library from our projects (npm run build doesn't run on Node 16 because of an old SASS dependency). I know it is asking a lot but it would be great if there was documentation on how to export blocks to a more modern implementation. I've tried running the eject command but you still end with the same dependency issues.

natedunn commented 2 years ago

yeah + 1 on deprecation or an honest attempt to pass to another maintainer. As the project currently stands, it will definitely lure a lot of folks into frustrations.

ahmadawais commented 2 years ago

I'm happy to add new maintainers. If anyone of you are interested. Let me know. If That doesn't work, I'll archive it.

This project requires a significant effort and I couldn't possibly do that alone and all for free especially as I stopped building anything with Gutenberg anymore.

Appreciate all the kind words y’all. --

:)

AHMAD AWAIS https://twitter.com/MrAhmadAwais/ ❯ VP of Developer Relations (DevRel & DX) RapidAPI https://rapidapi.com/company/about/ ❯ Multiple Award-winning Open Source GitHub Star https://ahmadawais.com/github-stars/ ❯ Node.js Foundation Community Committee Member ❯ OpenJS (Linux) Foundation Node.js Outreach Lead ❯ Google Developers Expert https://ahmadawais.com/google-developers-expert/ for Web Technologies ❯ WordPress Core Developer ❯ EE-CS Engineer ❯ Developer Edutainer https://ahmadawais.com/courses/ ;)

*→ Edutaining devs at AhmadAwais.com https://ahmadawais.com/ → Twitter https://twitter.com/MrAhmadAwais/*