fix(pack): loader resolve path

[fireairforce]

Summary

Updated PR: utooland/next.js#72

Test Plan

有个相对路径的测试 Case 会挂掉，符合目前的预期

[gemini-code-assist]

Summary of Changes

Hello @fireairforce, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical issue related to loader path resolution within the pack system, particularly for relative paths. It integrates a fix by updating the next.js subproject and adjusts existing snapshot tests, while also adding a new one, to accurately reflect the corrected behavior where previously misresolved modules now correctly report errors, ensuring the system's robustness.

Highlights

• Subproject Update: The next.js subproject commit has been updated from d362122e9643054428d93b8e7174bea3abbfd871 to be61779e9c293feb5ad46d0e9f78ee4318a61596, likely incorporating the core fix for loader path resolution.
• New Snapshot Test: A new snapshot test file (Error evaluating Node.js code-7dd645.txt) has been added to capture the expected error output when a Node.js module cannot be found via a relative path during loader evaluation.
• Updated Snapshot Output: An existing snapshot output (crates_pack-tests_tests_snapshot_fe2230b9.js) has been modified to now throw a MODULE_UNPARSABLE error for test.txt.js, indicating a corrected failure in module parsing due to the resolution issue.
• Source Map Adjustment: The corresponding source map (crates_pack-tests_tests_snapshot_fe2230b9.js.map) has been updated to reflect the changes in the JavaScript output, specifically removing source map entries for the module that is now correctly identified as unparsable.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

你好，感谢你的贡献。这次的 Pull Request 主要是修复了 pack 中 loader 的路径解析问题。主要的逻辑变更位于 next.js 子模块中，这部分代码没有包含在本次的 diff 里，因此无法直接审查。从变更的文件来看，你更新了相关的快照测试，使其符合修复后的预期行为（一个相对路径的测试用例现在会按预期失败）。这些快照的更新看起来是正确的，并且与 PR 的目标一致。由于没有看到核心逻辑的变更，本次审查主要基于快照文件。在这些文件中没有发现问题。