-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
53 additions
and
122 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -18,9 +18,6 @@ c:/data/tech/dev/project/MyWeb/projectSetup.txt). | |
| - [Initialize NPM Project] | ||
| - [Setup Blog Tooling] | ||
| - [Setup wiiBridges.com domain] | ||
| - [Publish to Web] | ||
| - [Setup New Feature Branch] | ||
|
|
||
|
|
||
| <!--- *** SECTION *************************************************************** ---> | ||
| # NPM Scripts | ||
|
|
@@ -595,120 +592,6 @@ wiiBridges.com domain. | |
| FYI: See details of this at c:/data/tech/isp/domain.GitHubDNS.txt. | ||
| <!--- *** SECTION *************************************************************** ---> | ||
| # Publish to Web | ||
| This section chronicles the steps in publishing **MyWeb** to wiiBridges.com. | ||
| AI: Most of the following needs to be reviewed and NIXed. What I typically do: | ||
| ``` | ||
| quick publish (from next3 branch) | ||
| * PUBLISH WEB ... do in PowerShell | ||
| $ cd C:\dev\MyWeb | ||
| $ npm run publish:web | ||
| * test: | ||
| https://wiibridges.com/ | ||
| ``` | ||
| **Feature Branch**: | ||
| Typically all development is done in a **feature branch**. If you are | ||
| about to deploy, presumably your branch is complete and documented. | ||
| 1. insure all tests are operational | ||
| ``` | ||
| $ npm run test | ||
| ``` | ||
| 2. finalize version -and- history notes: | ||
| - for the new version, use [semantic standards](http://semver.org/) | ||
| - update version in: | ||
| * `package.json` | ||
| * `blog/toc.md` (version is referenced at top) | ||
| * `blog/history.md` (within the "running" notes) | ||
| - review/finalize all blog impacted by change | ||
| * also insure README.md does NOT need to change | ||
| - optionally: save a link-neutral version of change history comments (to use in git tagging) | ||
| * pull from history.md _(normalizing any reference links)_ | ||
| * ALTERNATE: simply reference the history section (in the git tag) | ||
| EX: https://MyWeb.js.org/history.html#v0_1_0 | ||
| **main Branch**: | ||
| 1. issue PR (pull request) and merge to main branch | ||
| 2. sync main to local machine (where the deployment will occur) | ||
| 3. verify version is correct in: | ||
| * `package.json` | ||
| * `blog/toc.md` | ||
| * `blog/history.md` | ||
| 4. now, everything should be checked in to main and ready to publish | ||
| 5. tag the release (in github) | ||
| * verify the history page github links are correct (now that the tag exists) | ||
| 6. publish **MyWeb** to npm **_(THIS IS IT!)_**: | ||
| ``` | ||
| $ npm publish | ||
| + [email protected] | ||
| ``` | ||
| verify publish was successful | ||
| - receive email from npm | ||
| - npm package: https://www.npmjs.com/package/MyWeb | ||
| - unpkg.com: https://unpkg.com/MyWeb/ | ||
| 7. publish **MyWeb** page: | ||
| ``` | ||
| $ npm run blog:publish ... NO NO NO | ||
| ``` | ||
| verify publish site was successful | ||
| - https://MyWeb.js.org/ | ||
| * see new version | ||
| * see correct history | ||
| 8. optionally test the new package in an external project (by installing it) | ||
| <!--- *** SECTION *************************************************************** ---> | ||
| # Setup New Feature Branch | ||
| This section documents the steps to setup a new **feature branch** | ||
| (where all development is typically done): | ||
| 1. create a new branch (typically spawned from the "main" branch). | ||
| **EX**: `next7` | ||
| 2. devise "best guess" as to the next version number _(may be | ||
| premature, but this can subsequently change)_. | ||
| Reflect this in: | ||
| * `package.json` | ||
| * `blog/toc.md` (version is referenced at top) | ||
| * `blog/history.md` (within the "running" notes) | ||
| 3. setup new running Revision History (in `blog/history.md`) | ||
| This provides a place where we can incrementally maintain "running" | ||
| revision notes. | ||
| <!--- *** LINKS ***************************************************************** ---> | ||
| [NPM Scripts]: #npm-scripts | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters