Try/loading ecommerce module components directly #7
Conversation
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
… via the ecommerce js build
Bumps [react-router-dom](https://github.com/remix-run/react-router/tree/HEAD/packages/react-router-dom) from 7.1.1 to 7.1.3. - [Release notes](https://github.com/remix-run/react-router/releases) - [Changelog](https://github.com/remix-run/react-router/blob/main/packages/react-router-dom/CHANGELOG.md) - [Commits](https://github.com/remix-run/react-router/commits/[email protected]/packages/react-router-dom) --- updated-dependencies: - dependency-name: react-router-dom dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
…nents-directly * release/3.16.0: (23 commits) update to latest ecommerce and facebook modules revert to wp-scripts 27 and remove react-jsx-runtime polyfill adjust polyfill path and remove from normal webpack config happy lint happy life add jsx-runtime-polyfill for wp6.5 support - remove unused package bump installer version in composer to match lock update htaccess-manager package to fix 7.3 issue in php add missing package according to lint update version to 3.16.0 Composer(deps): Bump newfold-labs/wp-module-onboarding NPM Dev(deps-dev): Bump @tailwindcss/forms from 0.5.9 to 0.5.10 NPM(deps): Bump @wordpress/icons from 10.15.1 to 10.16.0 NPM(deps): Bump @wordpress/dom-ready from 4.14.0 to 4.16.0 Composer(deps): Bump newfold-labs/wp-module-coming-soon update remaining modules for runtime updates use latest fully released packages update to latest runtime and ecommerce module add @newfold packaged to tailwind config NPM Dev(deps-dev): Bump @wordpress/env from 10.14.0 to 10.16.0 update to runtime 1.1.3 release ... # Conflicts: # package-lock.json # package.json # src/app/pages/ecommerce/page.js # src/app/pages/home/freeAddonsSection.js # src/app/pages/home/index.js # src/app/pages/home/welcomeSection.js
Release 3.16.0
…p/react-router-dom-7.1.3 NPM(deps): Bump react-router-dom from 7.1.1 to 7.1.3
…irectly * develop: allow cypress matrix 60 min
…irectly * develop: NPM(deps): Bump react-router-dom from 7.1.1 to 7.1.3 # Conflicts: # package-lock.json
…ctly * main: (29 commits) add `set-version-bump` script to dist ignore add workflows label to dependabot for actions Revert "update composer package name for satis" update composer package name for satis update satis repo to newfold-labs update to latest facebook and migration modules version bump to 4.0.3 and module/dependency updates remove skipped tests update readme file with new repo paths remove stray whitespace i18n update for 4.0.1 update packages and modules to match 3.15.9 release version bump to 4.0.1 - corresponds to 3.15.9 release temporarily exclude notifications plugin-search tests update supported wp versions for Woo in cypress config new cypress project id for newfold bluehost plugin remove temporary test exclusion update coming soon and deactivation modules fix deactivation test with slug update and skip ecom tests for now skip deactivation survey test for now ... # Conflicts: # package-lock.json
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
This changes how the e-commerce module components are loaded in the plugin app. Before they were loaded via a package, but this updates it to directly load them in the plugin app like we do for other modules. We load the js components directly from the module in the vendor directory. This will need considerable testing on live sites.
This would eliminate the need for a js build package in the e-commerce module.
We'd also want to restructure the module and move the components out of the src directory and into a top-level components dir (src directories are usually excluded from builds). This effort is to bring all modules to a more consistent architecture.
Open Discussion
Is there a reason I'm missing that the build step is still required for the e-commerce module components? Removing it would simplify the plugin release process and make more of the modules lend components to the plugin rather than require a composer and npm package to run.
Before merging this we may want to have a larger discussion about best practices and module architecture. If we want to update this one to be more in line with the others, we should make sure we're following a best practice.
I've also had discussions about updating the plugin app to use slots and slotfills for modules to add components into assigned places, but I think we'd need some considerable updates to get to a place we can do this.
This PR picks up where bluehost/bluehost-wordpress-plugin#1515 left off.
Type of Change
Production
Development
Video
Checklist
Further comments