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

fix: replace polyfillio with fastly #1664

Merged
merged 1 commit into from
Mar 21, 2024
Merged

Conversation

saikumarrs
Copy link
Member

@saikumarrs saikumarrs commented Mar 21, 2024

PR Description

We're now using fastly polyfill service instead of polyfill.io.

Linear task (optional)

https://linear.app/rudderstack/issue/SDK-1405/use-fastly-instead-of-polyfillio

Cross Browser Tests

Please confirm you have tested for the following browsers:

  • Chrome
  • Firefox
  • IE11

Sanity Suite

  • All sanity suite test cases pass locally

Security

  • The code changed/added as part of this pull request won't create any security issues with how the software is being used.

Summary by CodeRabbit

  • Chores
    • Updated the source URL for polyfill scripts across various files to use a new domain (polyfill-fastly.io) for improved compatibility and performance. This affects the loading of essential web features in legacy and modern browsers alike.

@saikumarrs saikumarrs self-assigned this Mar 21, 2024
@saikumarrs saikumarrs requested a review from a team as a code owner March 21, 2024 12:38
Copy link
Contributor

coderabbitai bot commented Mar 21, 2024

Walkthrough

The overall change involves updating the source URL for polyfill scripts across various files, switching from https://polyfill.io to https://polyfill-fastly.io. This update aims to enhance compatibility and loading efficiency, affecting multiple packages and configurations within a larger project. The change is uniformly applied to ensure consistency and improve performance, particularly for legacy Safari browsers.

Changes

File Path Change Summary
.../public/index-legacy-only.html
.../public/index.html
.../rollup.config.mjs
.../rollup-configs/rollup.utilities.mjs
.../loading-scripts/src/index.ts
.../sanity-suite/public/v1.1/index-cdn.html
.../sanity-suite/public/v1.1/index-local.html
.../sanity-suite/public/v1.1/index-npm.html
.../sanity-suite/public/v1.1/integrations/index-cdn.html
.../sanity-suite/public/v1.1/integrations/index-local.html
.../sanity-suite/public/v1.1/integrations/index-npm.html
.../sanity-suite/public/v1.1/manualLoadCall/index-cdn.html
.../sanity-suite/public/v1.1/manualLoadCall/index-local.html
.../sanity-suite/public/v1.1/manualLoadCall/index-npm.html
.../sanity-suite/public/v3/index-cdn.html
.../sanity-suite/public/v3/index-local.html
.../sanity-suite/public/v3/index-npm.html
.../sanity-suite/public/v3/integrations/index-cdn.html
.../sanity-suite/public/v3/integrations/index-local.html
.../sanity-suite/public/v3/integrations/index-npm.html
.../sanity-suite/public/v3/manualLoadCall/index-cdn.html
.../sanity-suite/public/v3/manualLoadCall/index-local.html
.../sanity-suite/public/v3/manualLoadCall/index-npm.html
Updated polyfill script source URL from https://polyfill.io to https://polyfill-fastly.io.

🐰✨
In the code's woven maze, a change does sweep,
From polyfill.io to fastly, a leap.
Across the files, the updates dance,
A uniform step, enhancing performance by chance.
So cheers, my friends, to the shift so bright,
For smoother browsing, into the night.
🌟🐇

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit-tests for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit tests for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

Copy link

codecov bot commented Mar 21, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 53.89%. Comparing base (1f114a1) to head (ae53ff5).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1664   +/-   ##
========================================
  Coverage    53.89%   53.89%           
========================================
  Files          461      461           
  Lines        15588    15588           
  Branches      3096     3107   +11     
========================================
  Hits          8401     8401           
+ Misses        5871     5854   -17     
- Partials      1316     1333   +17     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 1f114a1 and ae53ff5.
Files selected for processing (23)
  • packages/analytics-js/public/index-legacy-only.html (1 hunks)
  • packages/analytics-js/public/index.html (1 hunks)
  • packages/analytics-js/rollup.config.mjs (1 hunks)
  • packages/analytics-v1.1/rollup-configs/rollup.utilities.mjs (1 hunks)
  • packages/loading-scripts/src/index.ts (2 hunks)
  • packages/sanity-suite/public/v1.1/index-cdn.html (1 hunks)
  • packages/sanity-suite/public/v1.1/index-local.html (1 hunks)
  • packages/sanity-suite/public/v1.1/index-npm.html (1 hunks)
  • packages/sanity-suite/public/v1.1/integrations/index-cdn.html (1 hunks)
  • packages/sanity-suite/public/v1.1/integrations/index-local.html (1 hunks)
  • packages/sanity-suite/public/v1.1/integrations/index-npm.html (1 hunks)
  • packages/sanity-suite/public/v1.1/manualLoadCall/index-cdn.html (1 hunks)
  • packages/sanity-suite/public/v1.1/manualLoadCall/index-local.html (1 hunks)
  • packages/sanity-suite/public/v1.1/manualLoadCall/index-npm.html (1 hunks)
  • packages/sanity-suite/public/v3/index-cdn.html (1 hunks)
  • packages/sanity-suite/public/v3/index-local.html (1 hunks)
  • packages/sanity-suite/public/v3/index-npm.html (1 hunks)
  • packages/sanity-suite/public/v3/integrations/index-cdn.html (1 hunks)
  • packages/sanity-suite/public/v3/integrations/index-local.html (1 hunks)
  • packages/sanity-suite/public/v3/integrations/index-npm.html (1 hunks)
  • packages/sanity-suite/public/v3/manualLoadCall/index-cdn.html (1 hunks)
  • packages/sanity-suite/public/v3/manualLoadCall/index-local.html (1 hunks)
  • packages/sanity-suite/public/v3/manualLoadCall/index-npm.html (1 hunks)
Additional comments: 24
packages/loading-scripts/src/index.ts (2)
  • 58-58: The globalThis polyfill implementation is a clever workaround for legacy Safari browsers. However, it's important to note that modifying Object.prototype can have unintended side effects in some cases. While this approach is generally safe, it's worth considering alternative polyfill strategies that avoid extending native prototypes if possible.
  • 86-86: The update to use https://polyfill-fastly.io/v3/polyfill.min.js is consistent with the PR's objective. However, it's crucial to verify that all features required by the application are supported by the Fastly polyfill service to ensure compatibility across all targeted browsers.
packages/sanity-suite/public/v1.1/index-npm.html (1)
  • 85-85: The update to the polyfill URL to https://polyfill-fastly.io/v3/polyfill.min.js is correctly implemented. Ensure that the specified features in the query parameters are fully supported by the Fastly service for all targeted browsers.
packages/sanity-suite/public/v3/index-npm.html (1)
  • 66-66: The update to the polyfill URL to https://polyfill-fastly.io/v3/polyfill.min.js is correctly implemented. Ensure that the specified features in the query parameters are fully supported by the Fastly service for all targeted browsers.
packages/sanity-suite/public/v1.1/index-cdn.html (1)
  • 109-109: The update to the polyfill URL to https://polyfill-fastly.io/v3/polyfill.min.js is correctly implemented. Ensure that the specified features in the query parameters are fully supported by the Fastly service for all targeted browsers.
packages/sanity-suite/public/v1.1/index-local.html (1)
  • 116-116: The update to the polyfill URL to https://polyfill-fastly.io/v3/polyfill.min.js is correctly implemented. Ensure that the specified features in the query parameters are fully supported by the Fastly service for all targeted browsers.
packages/sanity-suite/public/v1.1/integrations/index-npm.html (1)
  • 71-71: The update to the polyfill URL to https://polyfill-fastly.io/v3/polyfill.min.js is correctly implemented. Ensure that the specified features in the query parameters are fully supported by the Fastly service for all targeted browsers.
packages/sanity-suite/public/v1.1/manualLoadCall/index-npm.html (1)
  • 71-71: The update to the polyfill URL to https://polyfill-fastly.io/v3/polyfill.min.js is correctly implemented. Ensure that the specified features in the query parameters are fully supported by the Fastly service for all targeted browsers.
packages/analytics-v1.1/rollup-configs/rollup.utilities.mjs (1)
  • 24-24: The update to the polyfillIoUrl variable to use https://polyfill-fastly.io/v3/polyfill.min.js aligns with the PR's objective. It's important to ensure that all necessary polyfill features are supported by the Fastly service for compatibility across all targeted browsers.
packages/sanity-suite/public/v3/integrations/index-npm.html (1)
  • 57-57: The update from polyfill.io to polyfill-fastly.io is correctly implemented according to the PR objectives. Ensure that the version and features specified in the URL are compatible and necessary for the project.
packages/sanity-suite/public/v3/manualLoadCall/index-npm.html (1)
  • 57-57: The transition to polyfill-fastly.io is correctly applied here as well. It's important to verify that all specified features in the URL are indeed required for the project's functionality across supported browsers.
packages/sanity-suite/public/v3/index-local.html (1)
  • 66-66: The update to use polyfill-fastly.io is correctly implemented. As with the previous files, ensure the specified features are necessary and that the version is the most appropriate for the project's needs.
packages/sanity-suite/public/v3/index-cdn.html (1)
  • 66-66: The switch to polyfill-fastly.io is correctly done. It's good practice to periodically review the list of features requested from the polyfill service to ensure they are all still needed and to potentially optimize loading times.
packages/sanity-suite/public/v1.1/integrations/index-cdn.html (1)
  • 99-99: The update to polyfill-fastly.io is correctly applied. It's advisable to ensure that the polyfill features specified are aligned with the project's browser support policy.
packages/sanity-suite/public/v1.1/manualLoadCall/index-cdn.html (1)
  • 99-99: Correct implementation of the switch to polyfill-fastly.io. As always, verify that the features requested from the polyfill service are essential for the project.
packages/sanity-suite/public/v1.1/integrations/index-local.html (1)
  • 101-101: The transition to polyfill-fastly.io is correctly done here as well. Ensure that the polyfill features included in the URL are still relevant and necessary for the project.
packages/sanity-suite/public/v1.1/manualLoadCall/index-local.html (1)
  • 101-101: The update of the polyfill service URL from polyfill.io to polyfill-fastly.io is correctly implemented. This change aligns with the PR's objective to transition to Fastly's polyfill service for potentially improved performance or reliability. Ensure that this new URL is tested across the specified browsers (Chrome, Firefox, IE11) as part of the cross-browser testing checklist to confirm compatibility and functionality.
packages/sanity-suite/public/v3/integrations/index-cdn.html (1)
  • 66-66: The update from polyfill.io to polyfill-fastly.io aligns with the PR's objective. Ensure that the specified version (3.111.0) and features (Symbol, Promise) are supported and behave as expected on Fastly's service.
packages/sanity-suite/public/v3/manualLoadCall/index-cdn.html (1)
  • 66-66: The change to polyfill-fastly.io is consistent with the PR's goal. Verify that the version=3.111.0 and the features Symbol and Promise are fully compatible and performant with Fastly's polyfill service.
packages/sanity-suite/public/v3/integrations/index-local.html (1)
  • 66-66: The switch to polyfill-fastly.io is correctly implemented here. As with the other files, ensure compatibility and performance of the specified version=3.111.0 and features (Symbol, Promise) with Fastly's service.
packages/sanity-suite/public/v3/manualLoadCall/index-local.html (1)
  • 66-66: The update to polyfill-fastly.io is correctly applied. Confirm that version=3.111.0 and the requested features (Symbol, Promise) work as expected with Fastly's polyfill service.
packages/analytics-js/public/index-legacy-only.html (1)
  • 65-65: The transition to polyfill-fastly.io is properly executed in this file. Ensure that the version=3.111.0 and features (Symbol, Promise) specified are compatible and perform as expected with Fastly's polyfill service.
packages/analytics-js/public/index.html (1)
  • 65-65: The update of the polyfill service URL from polyfill.io to polyfill-fastly.io is noted. Ensure that comprehensive cross-browser testing, as mentioned in the PR description, has been conducted to verify that this change does not adversely affect the application's functionality across different environments.
packages/analytics-js/rollup.config.mjs (1)
  • 47-47: The update of the polyfillIoUrl variable from polyfill.io to polyfill-fastly.io in the Rollup configuration is noted. Ensure that the bundled output has been verified for correctness and that comprehensive cross-browser testing, as mentioned in the PR description, has been conducted to ensure that this change does not adversely affect the application's functionality across different environments.

Copy link

size-limit report 📦

Name Size (Base) Size (Current) Size Limit Status
Common Code - No bundling 15.81 KB 15.81 KB (0%) 16.5 KB
Remote Module Federation Mapping - CDN 330 B 330 B (0%) 512 B
Remote Module Federated Plugins - CDN 5.71 KB 5.71 KB (0%) 6 KB
Core ESM - NPM 7.64 KB 7.64 KB (0%) 8 KB
Core CJS - NPM 22.45 KB 22.45 KB (-0.02% ▼) 23 KB
Core - NPM 22.53 KB 22.53 KB (+0.03% ▲) 23 KB
Core Legacy - CDN 42.89 KB 42.89 KB (-0.02% ▼) 44 KB
Core - CDN 22.7 KB 22.7 KB (-0.03% ▼) 23 KB
Core (legacy build) - CDN - v1.1 31.45 KB 31.54 KB (+0.3% ▲) 32 KB
Core - NPM - v1.1 31.5 KB 31.55 KB (+0.18% ▲) 32 KB
Service Worker Module 22.64 KB 22.64 KB (0%) 24 KB
All Integrations (legacy build) - CDN 98.57 KB 98.57 KB (0%) 105 KB

@saikumarrs saikumarrs merged commit 24d3a0b into develop Mar 21, 2024
10 checks passed
@saikumarrs saikumarrs deleted the fix.use-fastly-sdk-1405 branch March 21, 2024 13:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants