Feature - eCommerce

[aulisius]

Proposed changes

This adds the eCommerce module to the plugin. Users of the plugin who are the on the eCommerce plans will be redirected to the new dashboard instead of the current /home/onboarding screens.

Type of Change

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

• I have read the CONTRIBUTING doc
• Linting and tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Pending Items

• Brand specific CSS tokens can be loaded via the module itself.

[wpscholar]

What exactly is this dependency referencing? I see the module package.json points to dist/index.js (https://github.com/newfold-labs/wp-module-ecommerce/blob/trunk/package.json#L7), but that doesn't exist in the repo and I don't see any packages released (https://github.com/newfold-labs/wp-module-ecommerce/packages).

[aulisius]

npm lets you specify git sources as package url. You can refer to the npm install documentation for more details.

npm does the following things for the given package

"@newfold-labs/wp-module-ecommerce": "newfold-labs/wp-module-ecommerce#v0.2.0"

• Search for newfold-labs/wp-module-ecommerce repo on GitHub
• Check if repo has a commit ref or tag with the value v0.2.0
• Download code from that commit
• Check if downloaded package.json file has a prepare script.
• Trigger the prepare script
• Clean up remaining files based on what files targets in package.json

In our case, the prepare script triggers the commands to produce the dist/ folder which contains the needed build artifacts.

[wpscholar]

@aulisius I've created a new feature/e-commerce branch in the main Bluehost repo. I've already merged the latest version of master into that branch. Since we've recently updated to a new version of React Router DOM, there may be an issue with the e-commerce onboarding page not loading (I couldn't see any of the new functionality except the "Site Status" in the admin bar).

So, here are a few things to do:

• Convert this PR to a draft
• Pull down the latest changes from the Bluehost feature/ecommerce branch to your local feature/ecommerce branch.
• Update your PR to merge into the Bluehost feature/ecommerce branch instead of master.
• Look into why the e-commerce onboarding page isn't displaying
• Update the README.md to include what steps are required to trigger the e-commerce onboarding flow from a development perspective. For example, making sure the install date is a particular value, the database information for plan type is set, etc.
• Update the DTS build to use wp-scripts
• Address any remaining TODOs in the code (I'm seeing this)
• Tag a new release of the e-commerce module once you're done making changes
• Update the e-commerce module version in the Bluehost plugin
• Move this PR from draft to ready for review

[aulisius]

@wpscholar regarding Update the DTS build to use wp-scripts, Does wp-scripts let you emit libraries instead of generated bundles that require to be loaded separately by PHP?

[wpscholar]

@aulisius Correct.

Here is the documentation for wp-scripts: https://developer.wordpress.org/block-editor/reference-guides/packages/packages-scripts/