-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Extensibility 🤌🏻] Make create-app
work with "extended templates"
#1205
Conversation
* v3: Drop npm 6 and node 14 from V3 (#1112) Upgrade lerna (#1111) add locale and currency to apiClients (#1107) Update test.yml (#1109) [V3] Invoke push action for v3 to `staging-v3` target (#1108) remove commerce api folder (#1105) # Conflicts: # package-lock.json # package.json # packages/commerce-sdk-react/package-lock.json # packages/commerce-sdk-react/package.json # packages/internal-lib-build/package-lock.json # packages/pwa-kit-create-app/package-lock.json # packages/pwa-kit-create-app/package.json # packages/pwa-kit-dev/package-lock.json # packages/pwa-kit-dev/package.json # packages/pwa-kit-react-sdk/package-lock.json # packages/pwa-kit-runtime/package-lock.json # packages/template-retail-react-app/app/mocks/mock-data.js # packages/template-retail-react-app/package-lock.json # packages/template-typescript-minimal/package-lock.json # packages/test-commerce-sdk-react/package-lock.json
…-rehaul * feature/template-extensibility: drop unnecessary pages/product-detail override updates from underlying template-retail-react-app add missing useToast (bad merge) add missing node engines update spike project's engines / regen v3 lockfiles resolve merge conflict merge conflict # Conflicts: # packages/spike-extendend-retail-app/pwa-kit/overrides/app/components/header/index.jsx # packages/spike-extendend-retail-app/pwa-kit/overrides/app/pages/product-detail/index.jsx
…orking, TODO next... cleanup
…inimum file project"
…ckly toggling some base constant values (e.g. categories shown on home page)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right now, the my-extended-retail-app
directory is still marked for deletion. I'm not sure the last time you merged back from develop
, but if needed we want to revert your deletion. We'll handle that deletion in a follow-up PR when we've done more testing and done more side-by-side comparison of generated (outside monorepo) projects to the my-extended-retail-app
.
packages/pwa-kit-create-app/assets/bootstrap/js/package.json.hbs
Outdated
Show resolved
Hide resolved
We are merging this without CI Windows passing. This is a known issue, but must be resolved for v3 to launch. A new GUS ticket is open here to track fixing this prior to an official / feature-complete v3 release: |
Description
Whats included in this PR?
my-extended-retail-app
template project (I'll talk about why below 👇🏻)pwa-kit-create-app
projecttemplate-retail-react-app
from dev to regular dependencies so that they would get installed when generating the project.3PP
Added
handlebars
the version in use already had an existing 3pp approval here.Why did I remove the
my-extended-retail-app
.Here are the reasons why having another projects template that is use essentially as a wrapper for the
template-retail-react-app
isn't idea.my-extended-retail-app
you'd have a very large package.json file.package.json
file problem without making themy-extended-retail-app
un-runnable in the monorepo. What this means, is that if we change the dev dependancies in thetemplate-retail-react-app
as we should, because lerna uses symbolic links for dependencies that are within the monorepo, the package resolution doesn't work correctly.How to Test-Drive this PR 🚘
It's very important that we test all the presets that the generator allows you to use. Below are the command you can run to locally create projects. For each command below we want to make sure that where are no errors generating, that the project generated is the one expected and the files expected, with the configuration expected. You should also run
npm start
for each to give. it a light smoke test.Before you run any of the below commands to generate projects, ensure you delete your
npx
cache:Additional Notes:
When choosing to generate the retail react app using the "demo" instance, extensibility will be used by default. The reason for doing this is 2 fold. First the demo preset isn't intended to be used as the project starting point for a partners project, it's intended to boot up the retail react app quickly so you can demo the site to someone, and not iterate on the code. Secondly, CI currently uses this preset to test that project generation works, we have to make sure that we don't block this preset by waiting for questions to be answered, this would break CI.
TODO's