Move the stream-compression package from wp-playground to php-wasm #895
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.
Stream Compression introduced in #851 has no dependencies on WordPress and can be used in any JavaScript project. It also makes sense as a dependency for some
@php-wasm
packages. This commit, therefore, moves it from thewp-playground
to thephp-wasm
npm namespace, making it reusable across the entire project.In addition, this adds a new
iterateFiles
function to the@php-wasm/universal
package, which allows iterating over the files in the PHP filesystem. It uses thestream-compression
package, which was some of the motivation for the move.This PR also ships eslint rules to keep the
stream-compression
package independent from the heavy@php-wasm/web
and@php-wasm/node
packages. This should enable using it in other project with a minimal dependency overhead of just@php-wasm/util
and@php-wasm/node-polyfills
.Testing instructions
Since the package isn't used anywhere yet, only confirm if the CI checks pass.