🚀 RELEASE: Full Featured create-guten-block utility!

.eslintignore

@@ -1,4 +1,4 @@
-**/*.min.js
 **/node_modules/**
 **/vendor/**
-**/block.build.js
+**/block.build.js
+**/*.min.js

.eslintrc.json

@@ -92,35 +92,35 @@
 			},
 			{
 				"selector": "ImportDeclaration[source.value=/^blocks$/]",
-				"message": "Use @wordpress/blocks as import path instead."
+				"message": "Use @wordpress/blocks as the import path instead."
 			},
 			{
 				"selector": "ImportDeclaration[source.value=/^components$/]",
-				"message": "Use @wordpress/components as import path instead."
+				"message": "Use @wordpress/components as the import path instead."
 			},
 			{
 				"selector": "ImportDeclaration[source.value=/^date$/]",
-				"message": "Use @wordpress/date as import path instead."
+				"message": "Use @wordpress/date as the import path instead."
 			},
 			{
 				"selector": "ImportDeclaration[source.value=/^editor$/]",
-				"message": "Use @wordpress/editor as import path instead."
+				"message": "Use @wordpress/editor as the import path instead."
 			},
 			{
 				"selector": "ImportDeclaration[source.value=/^element$/]",
-				"message": "Use @wordpress/element as import path instead."
+				"message": "Use @wordpress/element as the import path instead."
 			},
 			{
 				"selector": "ImportDeclaration[source.value=/^i18n$/]",
-				"message": "Use @wordpress/i18n as import path instead."
+				"message": "Use @wordpress/i18n as the import path instead."
 			},
 			{
 				"selector": "ImportDeclaration[source.value=/^data$/]",
-				"message": "Use @wordpress/data as import path instead."
+				"message": "Use @wordpress/data as the import path instead."
 			},
 			{
 				"selector": "ImportDeclaration[source.value=/^utils$/]",
-				"message": "Use @wordpress/utils as import path instead."
+				"message": "Use @wordpress/utils as the import path instead."
 			},
 			{
 				"selector":

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,113 @@
+<!--
+  PLEASE READ THE FIRST SECTION :-)
+-->
+
+### Is this a bug report?
+
+<!--
+  If you answered "Yes":
+
+    Please note that your issue will be fixed much faster if you spend about
+    half an hour preparing it, including the exact reproduction steps and a demo.
+
+    If you're in a hurry or don't feel confident, it's fine to report bugs with
+    less details, but this makes it less likely they'll get fixed soon.
+
+    In either case, please fill as many fields below as you can.
+
+  If you answered "No":
+
+    If this is a question or a discussion, you may delete this template and write in a free form.
+    Note that we don't provide help for webpack questions after ejecting.
+    You can find webpack docs at https://webpack.js.org/.
+-->
+
+
+(Write your answer here.)
+
+
+### Environment
+
+<!--
+  Please fill in all the relevant fields by running these commands in terminal.
+-->
+
+1. `node -v`:
+2. `npm -v`:
+3. `yarn --version` (if you use Yarn):
+4. `npm ls cgb-scripts` (if you haven’t ejected):
+
+Then, specify:
+
+1. Operating system:
+2. Browser and version (if relevant):
+
+
+### Steps to Reproduce
+
+<!--
+  How would you describe your issue to someone who doesn’t know you or your project?
+  Try to write a sequence of steps that anybody can repeat to see the issue.
+-->
+
+(Write your steps here:)
+
+1.
+2.
+3.
+
+
+### Expected Behavior
+
+<!--
+  How did you expect the tool to behave?
+  It’s fine if you’re not sure your understanding is correct.
+  Just write down what you thought would happen.
+-->
+
+(Write what you thought would happen.)
+
+
+### Actual Behavior
+
+<!--
+  Did something go wrong?
+  Is something broken, or not behaving as you expected?
+  Please attach screenshots if possible! They are extremely helpful for diagnosing issues.
+-->
+
+(Write what happened. Please add screenshots!)
+
+
+### Reproducible Demo
+
+<!--
+  If you can, please share a project that reproduces the issue.
+  This is the single most effective way to get an issue fixed soon.
+
+  There are two ways to do it:
+
+    * Create a new app and try to reproduce the issue in it.
+      This is useful if you roughly know where the problem is, or can’t share the real code.
+
+    * Or, copy your app and remove things until you’re left with the minimal reproducible demo.
+      This is useful for finding the root cause. You may then optionally create a new project.
+
+  This is a good guide to creating bug demos: https://stackoverflow.com/help/mcve
+  Once you’re done, push the project to GitHub and paste the link to it below:
+-->
+
+(Paste the link to an example project and exact instructions to reproduce the issue.)
+
+<!--
+  What happens if you skip this step?
+
+  We will try to help you, but in many cases it is impossible because crucial
+  information is missing. In that case we'll tag an issue as having a low priority,
+  and eventually close it if there is no clear direction.
+
+  We still appreciate the report though, as eventually somebody else might
+  create a reproducible example for it.
+
+  Thanks for helping us help you!
+-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,7 @@
+<!--
+Thank you for sending a PR!
+
+If you changed any code, please provide us with clear instructions on how you verified your changes work. Bonus points for screenshots! I mean that.
+
+Happy contributing!
+-->

.gitignore

@@ -55,11 +55,11 @@ assets/bower_components/*
 # NPM #
 ##########
 node_modules
+**/node_modules/**
 
 # Compiled Files and Build Dirs #
 ##########
 /README.html
-/build/
 
 # PhpStrom Project Files #
 .idea/
@@ -69,3 +69,17 @@ assets/sass/HTML
 assets/sass/Rails
 HTML
 Rails
+
+# CGB
+.idea/
+.vscode/
+node_modules/
+.DS_Store
+*.tgz
+my-app*
+template/src/__tests__/__snapshots__/
+lerna-debug.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+/.changelog

CONTRIBUTING.md

@@ -0,0 +1,45 @@
+# CONTRIBUTING to `create-guten-block`
+
+First of all, I'd like to welcome you for thinking about contributing to this project. I'd rather explain the flow of this project and explain all that in a later release (as right now I am focused at an early release).
+
+## 🔥 TL;DR
+
+- Git Clone `git clone https://github.com/ahmadawais/create-guten-block/`
+- `yarn`
+- `yarn create-guten-block demo-block`
+- `yarn updated`
+-
+
+## 📖 Details
+
+- `git clone https://github.com/ahmadawais/create-guten-block/`
+- `yarn` or `sudo yarn`
+    - Installs all the node packages and deps/devDeps in all the workspaces.
+- `yarn create-guten-block demo-block`
+    - This will run `tasks/cgb.js` file
+    - Which will run `./packages/create-guten-block/index.js`
+    - Which in turns runs `./packages/create-guten-block/createGutenBlock.js`
+    - That runs these functions
+        - `createPluginDir()`
+        - `copyTemplateToPluginDir()`
+        - `npmInstallBuild`
+        - And your new block plugin called `demo-block` gets added at the root of this project.
+- Now go to `cd demo-block`
+- Run `npm start` or `yarn start`
+- This will compile your code in `dist` and you're good to go.
+- Run `yarn updated` to check which npm packages were updated
+- Finally publish with 'yarn publishNPM' since yarn has some issues with publishing with lerna not sure why.
+- Check caveats for publishing.
+
+### 🤔 Caveats
+
+- Some issue with yarn not being able to publish via lerna
+- Use yarn with everything else but lerna
+- To publish always run via `npm` this command `npm run lerna`
+
+
+### 🐵 Other Stuff
+
+- Use `// @remove-file-on-eject` to do just that.
+- Use `// @remove-on-eject-begin` to do just that.
+- Use `// @remove-on-eject-end` to do just that.

README.md

@@ -3,6 +3,8 @@
 
 # Create-Guten-Block [WIP]
 
+[![lerna](https://img.shields.io/badge/maintained%20with-lerna-cc00ff.svg)](https://lernajs.io/)
+
 Create WordPress Gutenberg blocks with no build configuration.
 
 Create-Guten-Block has been tested to work on macOS, but must also work on Windows, and Linux.
@@ -32,11 +34,19 @@ Just create a project, and you’re good to go.
 
 ## Changelog
 
+### VERSION 2.0.0
+
+Work in progress.
+
 ### VERSION 1.0.0
 
 - ⚡️ NEW: NPM Module `create-guten-block`
 - ⚡️ NEW: Create WordPress plugin folder
 - ⚡️ NEW: Building WordPress plugin files
 - ⚡️ NEW: Build custom Gutenberg Block
 - ⚡️ NEW: Basic Webpack configurations
-- ⚡️ NEW: Dynamic WP Pluing and Gutenberg Block Names
+- ⚡️ NEW: Dynamic WP Pluing and Gutenberg Block Names
+
+### Docs Init
+
+- Install globally `npm install --global create-guten-block` (Run the same command again to update).