Skip to content
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

Remove modules infrastructure and UI from the plugin #1060

Merged
merged 14 commits into from
Mar 21, 2024
Merged
2 changes: 0 additions & 2 deletions .github/workflows/php-test-standalone-plugins.yml
Original file line number Diff line number Diff line change
Expand Up @@ -76,8 +76,6 @@ jobs:
node --version
composer --version
php -v
- name: Building standalone plugins
run: npm run build-plugins
Comment on lines -79 to -80
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are the plugins no longer needing to be built? In bin/plugin/commands/test-plugins.js it is not accounting for assets which may have been generated by Webpack as it is just copying the source files from /plugins to /build. It seems rather that test-plugins.js should be updated to reuse the output from npm run build-plugins which is already outputting the plugins into /build. cc @thelovekesh

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for pointing that out. It's on my list to address as a follow-up PR since it scratches the current one.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on what @thelovekesh wrote in #1060 (comment), do we even need this anymore? The purpose of the test-plugins script and this GitHub workflow was purely to test whether standalone plugins don't cause some weird fatal error when built from their modules.

Since we don't build modules into plugins anymore, I think this isn't useful any more. For that reason, I would suggest to remove the whole test-plugins script and everything around it. Since this is only removing more things, it would be great if you could do it as part of this PR.

I think some of the code changes in this PR are a bit confusing because they're changing those scripts when they don't really have a good purpose anymore as a whole.

- name: Running single site standalone plugin integration tests
run: npm run test-plugins
- name: Running multisite standalone plugin integration tests
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Performance Lab
![Performance Lab plugin banner with icon](https://user-images.githubusercontent.com/3531426/159084476-af352db4-192e-4927-a383-7f76bb3641df.png)

Monorepo for the [WordPress Performance Team](https://make.wordpress.org/performance/), primarily for the Performance Lab plugin, which is a collection of standalone performance modules.
Monorepo for the [WordPress Performance Team](https://make.wordpress.org/performance/), primarily for the Performance Lab plugin, which is a collection of standalone performance features.

Details about the Performance Lab plugin, including instructions for getting started and contributing, are available in the [Performance Team Handbook here](https://make.wordpress.org/performance/handbook/performance-lab/).

Expand Down
56 changes: 0 additions & 56 deletions admin/js/perflab-module-migration-notice.js

This file was deleted.

Loading
Loading