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

Do not inject Intl polyfill into ecma402-abstract package #21074

Merged
merged 1 commit into from
Jun 12, 2024

Conversation

steverep
Copy link
Member

@steverep steverep commented Jun 12, 2024

Proposed change

Fixes #21004 by also excluding the @formatjs/ecma402-abstract package from injection. That package is essentially helper functions for the polyfills. This bug was introduced in #20798 (basically a clerical error on my part). The polyfill was being injected there, essentially causing a circular reference and a promise that never completed as noticed in the issue.

As a note to myself and others testing these polyfills in the future, executing delete windown.Intl.DateTimeFormat, for example, is the proper way to test so that the shouldPolyfill functions get fully executed. Setting to undefined or just an if (true) is not sufficient. Also deleting more than one at a time can be important.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New feature (thank you!)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Example configuration

Additional information

Checklist

  • The code change is tested and works locally.
  • There is no commented out code in this PR.
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

Summary by CodeRabbit

  • Chores
    • Improved build process by updating exclusion patterns for internationalization modules, enhancing compatibility and performance.

Copy link
Contributor

coderabbitai bot commented Jun 12, 2024

Walkthrough

Walkthrough

The recent update to the build-scripts/bundle.cjs file enhances the build process by refining the babelOptions configuration. Specifically, the exclusion pattern for internationalization-related modules has been broadened to include @formatjs/ecma402-abstract along with @formatjs/intl-\\w+. This change aims to improve compatibility and performance during the build process by excluding additional unnecessary modules.

Changes

File Change Summary
build-scripts/bundle.cjs Updated babelOptions export to extend the exclusion pattern to include @formatjs/ecma402-abstract.

Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between 067e179 and 3056e2b.

Files selected for processing (1)
  • build-scripts/bundle.cjs (1 hunks)
Additional context used
Path-based instructions (1)
build-scripts/bundle.cjs (4)

Pattern */**(html|markdown|md): - For instructional content in documentation, use a direct and authoritative tone. Avoid expressions of politeness such as 'may' or 'please', and ensure the goal of the instruction is fronted.

  • Apply the Microsoft Style Guide to ensure documentation maintains clarity and conciseness.
  • In step-by-step instructions, front the location phrase in the instructional sentence.
  • In step-by-step instructions, front the 'goal' in the instructional sentence.
  • In step-by-step instructions, if in doubt what to front, front the 'goal' before the location phrase in the instructional sentence.
  • do not hyphenate terms like 'top-right' or 'bottom-left' with 'corner'

Pattern */**(html|markdown|md): - Use bold to mark UI strings.

  • If "" are used to mark UI strings, replace them by bold.

Pattern */**(html|markdown|md): - Be brief in your replies and don't add fluff like "thank you for..." and "Please let me know if"


Pattern */**(html|markdown|md): - Use sentence-style capitalization also in headings.

Biome
build-scripts/bundle.cjs

[error] 1-1: A Node.js builtin module should be imported with the node: protocol. (lint/style/useNodejsImportProtocol)

Using the node: protocol is more explicit and signals that the imported module belongs to Node.js.
Unsafe fix: Add the node: protocol.


[error] 216-216: Template literals are preferred over string concatenation. (lint/style/useTemplate)

Unsafe fix: Use a template literal.


[error] 237-237: Template literals are preferred over string concatenation. (lint/style/useTemplate)

Unsafe fix: Use a template literal.


[error] 267-267: Template literals are preferred over string concatenation. (lint/style/useTemplate)

Unsafe fix: Use a template literal.


[error] 281-281: Template literals are preferred over string concatenation. (lint/style/useTemplate)

Unsafe fix: Use a template literal.


[error] 301-301: Template literals are preferred over string concatenation. (lint/style/useTemplate)

Unsafe fix: Use a template literal.

Additional comments not posted (1)
build-scripts/bundle.cjs (1)

160-160: The update to the exclusion pattern in babelOptions to include @formatjs/ecma402-abstract is a good fix for the circular reference issue.


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 testing code 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 testing code 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 testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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 an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @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.
  • Please see the configuration documentation for more information.
  • 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/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added the Build Related to building the code label Jun 12, 2024
@steverep steverep added this to the 2024.6 milestone Jun 12, 2024
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.

Actionable comments posted: 0

Outside diff range comments (2)
build-scripts/bundle.cjs (2)

Line range hint 1-1: Use the node: protocol for importing Node.js built-in modules.

- const path = require("path");
+ const path = require("node:path");

Line range hint 216-216: Use template literals instead of string concatenation for better readability and performance.

- const ref = env.version().endsWith("dev") ? process.env.GITHUB_SHA || "dev" : env.version();
+ const ref = env.version().endsWith("dev") ? `${process.env.GITHUB_SHA || "dev"}` : `${env.version()}`;

- const name = "frontend" + nameSuffix(latestBuild);
+ const name = `frontend${nameSuffix(latestBuild)}`;

- const name = "demo" + nameSuffix(latestBuild);
+ const name = `demo${nameSuffix(latestBuild)}`;

- const name = "cast" + nameSuffix(latestBuild);
+ const name = `cast${nameSuffix(latestBuild)}`;

- const name = "supervisor" + nameSuffix(latestBuild);
+ const name = `supervisor${nameSuffix(latestBuild)}`;

- const name = "gallery" + nameSuffix(latestBuild);
+ const name = `gallery${nameSuffix(latestBuild)}`;

Also applies to: 237-237, 267-267, 281-281, 301-301

@balloob balloob merged commit 3e1227b into dev Jun 12, 2024
14 checks passed
@balloob balloob deleted the do-not-inject-ecma402-abstract branch June 12, 2024 18:45
@deltazerorsan
Copy link

2024.6.3 working in iOS 12.5.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Build Related to building the code cla-signed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error while loading page lovelace. on 2024.6.0
3 participants