Skip to content
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.

chore: updated SvelteKit framework info #818

Merged
merged 1 commit into from Oct 4, 2022

Conversation

nickytonline
Copy link
Contributor

πŸŽ‰ Thanks for submitting a pull request! πŸŽ‰

Summary

Updates the framework info for SvelteKit. I confirmed these changes with Brittney.

Fixes #817


For us to review and ship your PR efficiently, please perform the following steps:

  • Open a bug/issue before writing your code πŸ§‘β€πŸ’». This
    ensures we can discuss the changes and get feedback from everyone that should be involved. If you`re fixing a
    typo or something that`s on fire πŸ”₯ (e.g. incident related), you can skip this step.
  • Read the contribution guidelines πŸ“–. This ensures your code follows our style guide and
    passes our tests.
  • Update or add tests (if any source code was changed or added) πŸ§ͺ
  • Update or add documentation (if features were changed or added) πŸ“
  • Make sure the status checks below are successful βœ…

A picture of a cute animal (not mandatory, but encouraged)

@github-actions github-actions bot added the type: chore work needed to keep the product and development running smoothly label Oct 4, 2022
@@ -4,7 +4,7 @@
"category": "build_tool",
"detect": {
"npmDependencies": ["vite"],
"excludedNpmDependencies": ["@shopify/hydrogen", "@builder.io/qwik", "solid-start", "solid-js"],
"excludedNpmDependencies": ["@shopify/hydrogen", "@builder.io/qwik", "solid-start", "solid-js", "@sveltejs/kit"],
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Adding SvelteKit as an excluded dependency so it doesn't get picked up by the vite framework info config.

"command": "svelte-kit build",
"directory": "build"
"command": "vite build",
"directory": ".svelte-kit"
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we have to worry about sites with older versions of SvelteKit breaking with this change? I know we had a similar conversation with respect to vite but I think there might be a lot more users that this change would affect.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I had thought about this, kind of like the PR #792, but in this case, these are the settings for the first official release for SvelteKit.

This also brings up the conversation again about potentially versioning framework information.

Choose a reason for hiding this comment

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

This is something I mentioned to Nick in slack. There is a workaround by adding the targetPort to the netlify,toml file that can be added by anyone on an older version, but this will fix it so new updated sites don't have to do the workaround to get the CLI command to work.

Copy link
Contributor

Choose a reason for hiding this comment

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

Got it, thanks both!

Copy link

@brittneypostma brittneypostma left a comment

Choose a reason for hiding this comment

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

Looks good to me.

@kodiakhq kodiakhq bot merged commit acd85cf into main Oct 4, 2022
@kodiakhq kodiakhq bot deleted the nickytonline/update-svelte-kit-framework-info branch October 4, 2022 16:19
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
automerge type: chore work needed to keep the product and development running smoothly
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SvelteKit framework info is out of date
3 participants