-
Notifications
You must be signed in to change notification settings - Fork 130
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Copy extension build output to legacy location (#4890)
### WHY are these changes introduced? To maintain backward compatibility with existing extension build processes while transitioning to a new output directory structure under `.shopify/bundle/<ext_id>/dist`. ### WHAT is this pull request doing? Introduces a file copying mechanism that preserves extension build outputs in their original locations while also storing them in the new centralized directory. This ensures that: - All extension outputs are available in a single directory for bundling - Legacy flows depending on the original output locations continue to work - Source maps and build artifacts remain easily accessible ### How to test your changes? 1. Run `dev` (having ui extensions) 2. Verify that build outputs appear in both: - The new `.shopify/bundle/<ext_id>/dist` directory - The `dist` folder inside the extension directory. 3. Confirm that source maps are accessible in both locations 4. Test that hot reloading continues to work as expected and both outputs are updated. ### Checklist - [ ] I've considered possible cross-platform impacts (Mac, Linux, Windows) - [ ] I've considered possible [documentation](https://shopify.dev) changes
- Loading branch information
Showing
4 changed files
with
42 additions
and
17 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
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