Skip to content

Conversation

@9aoy
Copy link
Contributor

@9aoy 9aoy commented Nov 5, 2025

Summary

support npm package names in setupFiles.

Related Links

close: #669

Checklist

  • Tests updated (or not required).
  • Documentation updated (or not required).

Copilot AI review requested due to automatic review settings November 5, 2025 09:43
@netlify
Copy link

netlify bot commented Nov 5, 2025

Deploy Preview for rstest-dev ready!

Name Link
🔨 Latest commit 932a282
🔍 Latest deploy log https://app.netlify.com/projects/rstest-dev/deploys/690b1c4996697c0008776316
😎 Deploy Preview https://deploy-preview-671--rstest-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR fixes a bug in the getSetupFiles function where setup files specified as package names were not being resolved to their actual paths. Previously, the code called tryResolve but discarded its return value, always using the original setupFile string instead of the resolved path.

  • Caches the result of tryResolve to avoid calling it twice and uses the resolved path instead of the original package name

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@9aoy 9aoy merged commit 425e354 into main Nov 5, 2025
23 checks passed
@9aoy 9aoy deleted the resolve-setup-module-path branch November 5, 2025 10:13
@9aoy 9aoy mentioned this pull request Nov 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature]: Support npm package names in setupFiles

2 participants