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

Configuration and manifest do not load when using a js build tool #957

Open
1 of 3 tasks
hackartisan opened this issue Jan 25, 2024 · 1 comment
Open
1 of 3 tasks

Comments

@hackartisan
Copy link

UV version:
4.0.23 and above

I'm submitting a:

  • bug report => please fork one of these codesandbox examples with a repro of your issue and include a link to it below
  • feature request => please use the user stories repo
  • support request => Please do not submit support requests here, use stackoverflow

Current behavior:
Config cannot load when using a js build tool

Expected behavior:
Config should still be able to load

Steps to reproduce:

Here's a codesandbox replicating the error, based on the vite example, all we did was increment the UV version in the package.json:

https://codesandbox.io/p/sandbox/uv-vite-multiple-example-forked-yv9ryr
Related code:
The error was introduced in this PR -- it appears that the relative path navigation in loadconfig works fine when fetching the release from a cdn but not when js is loaded through a build tool like vite. Other build tools (webpack, etc) would probably also not work.

Other information:

@hackartisan
Copy link
Author

Also, it would be good to add the vite example to the build process for new PRs.

The uv-nextjs-example PR introducing this error also shows the bug.

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

No branches or pull requests

1 participant