Idea: Execute optimization automatically after static-content:deploy
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 171
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
## This issue is a:
- [ ] Bug
- [x] Feature suggestion
- [ ] Documentation issue
- [ ] Other (Please Specify)
## Description
- once the build config is present somewhere in the project, probably all steps after that could be automated by hooking into the static-content deploy process of magento
- Maybe add a flag to setup:static-content:deploy command to trigger optimization
## Preconditions
- requirejs has to be installed and available as command
- magento js minification disabled (could probably be automated)
- static content deploy mode can possibly not be compact
## Steps after a Theme is deployed
- copy theme to _source
- execute rjs optimizer
- remove _source dir?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin with Magento's setup:static-content:deploy entry point and the existing build configuration and RequireJS optimizer prerequisites described here. Determine whether automation belongs behind a new flag or the deploy hook, then verify the listed copy, optimization, and cleanup steps.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100