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] consider paths.assets for version.json #4234

Merged
merged 4 commits into from Mar 5, 2022

Conversation

baseballyama
Copy link
Member

fix: #4188

Checklist

I checked behavior with adapter-node.

  • It can fetch version.json if kit.paths.assets has custom value
  • It can fetch version.json if kit.paths.assets doesn't set value

I couldn't find how to write tests.
So could you please teach me if there are some sample existing tests?

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
  • This message body should clearly illustrate what problems it solves.
  • Ideally, include a test that fails without this PR but passes with it.

Tests

  • Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

  • If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

@changeset-bot
Copy link

changeset-bot bot commented Mar 5, 2022

🦋 Changeset detected

Latest commit: a5b8ee0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@sveltejs/kit Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@Rich-Harris
Copy link
Member

Thanks — this would fix the issue (agree that it's quite hard to add a test for this, I suppose we could set paths.assets to http://localhost:${TEST_PORT}/assets and check it works, but that feels like a task for another day) but it's not 100% future-proof, because one day we'd like to introduce dynamic basepaths (#595) so that Kit apps work on IPFS/the internet archive/situations where the basepath is set by an environment variable/etc.

I think we can support that by just using paths.assets instead of paths.base (if assets is unset, it defaults to base) — 5cb8870

@baseballyama
Copy link
Member Author

baseballyama commented Mar 5, 2022

VITE_SVELTEKIT_APP_VERSION_FILE is super specific name, so I assigned complete path.
But I agree with you that building complete path at runtime is more flexible if we consider dynamic basepath.👍

Regarding testing, I remember that there have been some issues regarding basepath in the past.,
so if we have a testing mechanism, it would be great.

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.

version.json doesn't consider paths.assets
2 participants