chore: cleanups - pnpm removal - webpack polyfill - ci update #1521
  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.
  
    
  
    
What kind of change does this PR introduce?
Package Management Cleanup & Webpack Optimization
pnpmfrom this repository to standardize onnpmas the sole package managerprocess: 'process/browser'webpack polyfill that was causing unnecessary bundle bloatWhat is the current behavior?
npmandpnpm), which creates inconsistency and potential dependency resolution issues. The CI usesnpmwhilepnpmappears to have been introduced accidentally in a previous PR (fix: Bump up realtime-js #1418)process: 'process/browser'polyfill that was originally added in PR Add back UMD to npm builds #72 in November 2020 for UMD build compatibility but is no longer necessary with modern webpackWhat is the new behavior?
npmis used throughout the repository, ensuring consistency between development and CI environmentsAdditional context
Why removing the webpack polyfill is safe:
process.versionin one location (src/index.ts) for Node.js deprecation warnings, which only runs in Node.js environments anywayBenefits of this cleanup:
The PR also updates documentation in README.md to reflect the
npm-only approach and includes various lock file updates that ensure consistent dependency resolution across different environments.