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 install commands for different yarn versions #525

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

alexeyr-ci
Copy link

@alexeyr-ci alexeyr-ci commented Nov 21, 2024

Summary

The install command given for Yarn Classic only works for Yarn Berry. The command given for Yarn Berry works, but only due to backward compatibility. See https://yarnpkg.com/cli/install:

If the --immutable option is set (defaults to true on CI), Yarn will abort with an error exit code if the lockfile was to be modified (other paths can be added using the immutablePatterns configuration setting). For backward compatibility we offer an alias under the name of --frozen-lockfile, but it will be removed in a later release.

Separately, removed a duplicate sentence.

Pull Request checklist

  • [ ] Add/update test to cover these changes
  • Update documentation
  • [ ] Update CHANGELOG file

Other Information

Summary by CodeRabbit

  • Documentation
    • Updated upgrade guide for Shakapacker from v7 to v8, detailing significant changes and best practices.
    • Emphasized the importance of setting the SHAKAPACKER_ASSET_HOST environment variable.
    • Clarified the necessity of the packageManager property in package.json.
    • Noted the renaming of the check_yarn rake task to check_manager.
    • Highlighted the requirement for manual installation of JavaScript dependencies prior to asset compilation.

The install command given for Yarn Classic only works for Yarn Berry. The command given for Yarn Berry works, but only due to backward compatibility.
Copy link

coderabbitai bot commented Nov 21, 2024

Walkthrough

The changes in this pull request detail the upgrade from Shakapacker v7 to v8, highlighting the removal of deprecated functions, a shift to package manager-agnostic dependency management, and the discontinuation of support for Ruby 2.6 and Node v12. Key updates include the necessity of setting the SHAKAPACKER_ASSET_HOST environment variable, the renaming of the check_yarn rake task to check_manager, and the removal of all references to webpacker. Additionally, automatic installation of JavaScript dependencies during asset precompilation has been eliminated, requiring users to manage dependencies manually.

Changes

File Change Summary
docs/v8_upgrade.md - Removed deprecated functions and features.
- Transitioned to package manager-agnostic approach.
- Discontinued support for Ruby 2.6 and Node v12.
- Retained behavior of omitting CDN asset host but requires careful asset compilation management.
- packageManager property in package.json is now essential.
- Renamed check_yarn to check_manager.
- Removed all references to webpacker.
- JavaScript dependencies no longer installed automatically during assets:precompile.
- Enabled ensure_consistent_versioning by default.
- Updated function usage: globalMutableWebpackConfiggenerateWebpackConfig().
- Stripped additional_paths and removed several miscellaneous functions.

Possibly related PRs

  • Allow loading webpack.config.ts if present #524: Allow loading webpack.config.ts if present - This PR introduces the ability to load a TypeScript configuration file for webpack, which aligns with the main PR's changes regarding the handling of configuration files and the transition to a more flexible setup.

Suggested reviewers

  • G-Rath
  • justin808
  • tomdracz

🐰 In the garden, changes bloom,
Shakapacker sheds its gloom.
From v7 to v8, we leap and bound,
With new paths and tasks profound.
Dependencies we now must tend,
A brighter future, around the bend! 🌸


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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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 using 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.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

Copy link

@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: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between f829152 and 3d1caae.

📒 Files selected for processing (1)
  • docs/v8_upgrade.md (2 hunks)
🔇 Additional comments (1)
docs/v8_upgrade.md (1)

24-24: LGTM! Valuable documentation about CDN gotchas.

This addition provides crucial information about the limitations of using empty SHAKAPACKER_ASSET_HOST with dynamic imports and static assets, along with clear workarounds.

Comment on lines +103 to +106
raise if File.exist?("package.json") && !(system "yarn install --frozen-lockfile")

# yarn v2+ (berry)
raise if File.exist?("package.json") && !(system "yarn install --frozen-lockfile")
raise if File.exist?("package.json") && !(system "yarn install --immutable")
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix Yarn install commands documentation

The current documentation might be confusing as it suggests different flags for different Yarn versions. According to Yarn's documentation:

  • For Yarn Classic (1.x): --frozen-lockfile is the correct flag
  • For Yarn Berry (2+): Both --immutable and --frozen-lockfile work (the latter for backward compatibility)

To make this clearer, consider this revision:

    # yarn v1.x (classic)
-    raise if File.exist?("package.json") && !(system "yarn install --frozen-lockfile")
+    # Use --frozen-lockfile for Yarn Classic
+    raise if File.exist?("package.json") && !(system "yarn install --frozen-lockfile")

    # yarn v2+ (berry)
-    raise if File.exist?("package.json") && !(system "yarn install --immutable")
+    # Both --immutable and --frozen-lockfile (for backward compatibility) work
+    raise if File.exist?("package.json") && !(system "yarn install --immutable")
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
raise if File.exist?("package.json") && !(system "yarn install --frozen-lockfile")
# yarn v2+ (berry)
raise if File.exist?("package.json") && !(system "yarn install --frozen-lockfile")
raise if File.exist?("package.json") && !(system "yarn install --immutable")
# yarn v1.x (classic)
# Use --frozen-lockfile for Yarn Classic
raise if File.exist?("package.json") && !(system "yarn install --frozen-lockfile")
# yarn v2+ (berry)
# Both --immutable and --frozen-lockfile (for backward compatibility) work
raise if File.exist?("package.json") && !(system "yarn install --immutable")

Copy link
Contributor

@G-Rath G-Rath left a comment

Choose a reason for hiding this comment

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

whoops, thanks for catching this mix up!

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.

3 participants