primordic/IssueDupesLite huggingface dataset:
Repository: supabase/supabase

Issue #6401: Edge-Functions - Terminal Overflow
Created: 2022-04-11T10:44:48Z
Bug report
Describe the bug
On the edge-functions page on the section 'Anatomy of an Edge Function', the terminal overflows horizontally.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

go to edge-functions page
Go down to 'Anatomy of an Edge Function'
You'll see the terminal to the right overflowing

Expected behavior
It appears the gap seems too big. If gap: 4rem; / gap-16 is applied then the overflow seems to align better.
Screenshots
Current page:

Proposed change:

System information

OS: MacOS
Browser: Chrome

Additional context
I'll create a pull request for this.

Duplicate issue #6495: Content on edge functions page overflow
Created: 2022-04-18T23:03:26Z
Bug report
Describe the bug
On smaller screens, the content on the edge functions page is overflowing.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Go to edge-functions
Scroll down to Anatomy of an Edge Function section
See overflow

Expected behavior
Content not overflowing on smaller screens. Maybe make the content scrollable or just smaller.
Screenshots

  
    
    

    Screen.Recording.2022-04-17.at.1.47.00.PM.mov
    
  

  

  


System information

OS: Any (test on mac)
Browser: Any (test on firefox)
Version of supabase-js: N/A
Version of Node.js: N/A

Additional context
Anyone is welcome to work on this issue.

Closing comment (2022-04-19T10:45:12Z): yeah, seems to be a duplicate of #6401
Let's use that one 👍
Repository: supabase/supabase

Issue #4317: "function hooks (alpha)" has disappeared from the docs
Created: 2021-12-05T20:54:47Z
Improve documentation
Link
https://supabase.com/docs/blog/2021/07/30/supabase-functions-updates#function-hooks-alpha
Describe the problem
That page is missing, even though it shows up in the search results.
Describe the improvement
Recover/restore it, or remove it from the search results.
Additional context
It might be good to link to this doc once it's back up from the blog post announcing the feature's alpha.

Duplicate issue #4957: Doc search sometimes link to non-existnent pages
Created: 2022-01-12T22:14:13Z
Improve documentation
Link
https://supabase.com/docs/blog/2021/12/01/realtime-row-level-security-in-postgresql#realtime-design
Describe the problem
I was searching for how to use the real-time API live, on stream, when I ran into this. The doc is missing; it may be a blocker, but I figured I'd raise the issue before trying to find a workaround.
Describe the improvement
Create the page, so it exists or remove the page from the search index.
Additional context

Other pages that don't work

https://supabase.com/docs/blog/2021/09/10/supabase-beta-august-2021#realtime-security-codename-walrus
https://supabase.com/docs/blog/2021/12/15/beta-november-2021-launch-week-recap#realtime-row-level-security
https://supabase.com/docs/blog/2021/12/17/holiday-hackdays-winners-2021#best-realtime-project

I'm sure that there are others, but I'm sure y'all can find more simply by searching and testing if the link leads to a doc that exists.

Closing comment (2022-01-13T07:07:12Z): Duplicate #4317
Repository: supabase/supabase

Issue #4248: Can't get multiple records from a supabase function
Created: 2021-12-02T15:46:32Z
Discussed in #4245

Originally posted by RobertBrunhage December  2, 2021
I have the following function that returns a record but this only seems to return the first record, instead of all of them.

I've tried the same query in the SQL editor/tester and during that it returns multiple records.
How do I make the function return all the records that satisfy the query?

Duplicate issue #4865: Create functions that returns an array
Created: 2022-01-07T17:44:01Z
Feature request
Is your feature request related to a problem? Please describe.
Today I was trying to write a postgres function with the supabase function editor, but discovered that it is currently not possible to return an array.
Describe the solution you'd like
Add a toggle button labeled something like: is array.
Like the toggle button for creating a new column in the table editor:

Additional context
This is the current dropdown of return types:

Closing comment (2022-07-09T13:10:34Z): that it is currently not possible to return an array

I assume that you would like to return a set of rows right @vinyll ?
This is definitely possible! https://supabase.com/docs/guides/database/functions#returning-data-sets
Did you try this one yet?
Take note that in Postgres the "array type" is different from returning a "set of rows". If you call the database function using the RPC supabase-js: https://supabase.com/docs/reference/javascript/rpc

Is this somehow related to #4248?

This could be the case - for now you will need to use the SQL editor to write your Postgres function
Repository: supabase/supabase

Issue #2214: Missing Hyperlink in Connection Pooling Config
Created: 2021-07-04T09:18:47Z
Missing Hyperlink in Connection Pooling Config
On https://app.supabase.io/project/[id]/database/pooling there is a missing hyperlink.
For the Pool Mode Option, you say "To find out the most suitable mode for your use case, click here", but there is no link at "click here".
To Reproduce

Go to https://app.supabase.io/project/[id]/database/pooling

Expected behavior
There should be a hyperlink to the docs that describes what the Pool Mode options is.

Duplicate issue #2737: 'click here' text in Supabase dashboard is missing link to docs
Created: 2021-08-06T03:46:55Z
Bug report
Describe the bug
The click here text should be a link to documentation, but it is not linked at all.
To Reproduce
It can be viewed while logged into Supabase, (at https://app.supabase.io/project/<your-project-id>/database/pooling), in the description of the Pool Mode section.
Steps to reproduce the behavior, please provide code snippets or a repository:

Login to Supabase, and go to Database > Connection Pooling (https://app.supabase.io/project/<your-project-id>/database/pooling)
Navigate to the Configuration section, near the top of the page.
Within that section, scroll down to Pool Mode.
Note that the description below the text field is missing the link on words click here.

Text snippet:
Specify when a connection can be returned to the pool. To find out the most suitable mode for your use case, click here.

Expected behavior
The words click here should lead to docs that can help the user learn which pool mode to choose. The document below is likely a good fit.

https://supabase.io/docs/guides/database/connecting/connection-pooling

Screenshots

System information

macOS
Chrome

Additional context
N/A

Closing comment (2021-08-06T04:29:57Z): duplicate #2214
Repository: supabase/supabase

Issue #31194: Unwanted horizontal scrollbar in top bar
Created: 2024-12-17T08:56:58Z
Bug report


 I confirm this is a bug with Supabase, not with my own application.
 I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
Only started noticing this issue today. Occurs when my laptop (2020 M1 Macbook Air) has a mouse plugged in (which causes Chromium-based browsers to show a vertical scrollbar in all scrollable areas). Similar to #20167.
To Reproduce

Use macOS, plug in a mouse
Go to SB dashboard
Look at the top bar

Expected behavior
There is no horizontal scrollbar in the top bar when the screen width is not above the breakpoint at which side-scrolling is enabled.
Screenshots
Desired behavior (screenshot without mouse plugged in):

Current behavior (screenshot with mouse plugged in):

System information

OS: macOS Sequoia
Browser: Brave (this probably happens on other Chromium-based browsers too, though)

Additional context
N/A

Duplicate issue #31254: Supabase Dashboard UI Issue in the top navigation bar
Created: 2024-12-19T19:33:40Z
Bug report


 I confirm this is a bug with Supabase, not with my own application.
 I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
I think this is unwanted scrollbar.

To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Go to 'https://supabase.com/dashboard/projects'
Click on 'Pick any project'
Go to any page like as "Table Editor" or "Project Setting"
See error

Expected behavior
This scrollbar is absolutely unncessary.
Screenshots
Already shared the screenshot in the issue descrption
System information

OS: Windows
Browser (if applies): Chrome
Version of supabase-js: *
Version of Node.js: *

Additional context
Add any other context about the problem here.

Closing comment (2024-12-19T20:02:37Z): Hi @xspace-solution - Thank you for opening this issue. This should be fixed in #31253.
Also this has been reported in #31194, I'm going this for now but again thank you for taking the time to open the issue!
Repository: supabase/supabase

Issue #11656: Self-Hosted Studio makes requests to `localhost:8000` instead of `EXTERNAL_API_URL`
Created: 2023-01-13T23:09:31Z
Bug report
Describe the bug
When loading tables and buckets, the Studio makes requests to http://localhost:8000/storage/v1/bucket and http://localhost:8000/rest/v1/ instead of https://kong.example.com/rest/v1/. This means that if I visit the Studio externally it will be stuck on Connecting to default project because only the host computer can reach localhost.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Clone the master branch
Create subdomains that point to point 8000 and 3000
Use the subdomain that points to 8000 as API_EXTERNAL_URL and SUPABASE_PUBLIC_URL  in .env
docker compose up -d
Visit the 3000 subdomain on the host computer and it works but you will see in Network that the requests are made to localhost:8000
Visit the 3000 subdomain on a different computer and it does not work,

You will see in Network that the requests are made to localhost:8000
External computer cannot reach that
Everthing will show Connecting to default project



Expected behavior
The Studio should use the correct URL to make requests.
Screenshots

Additional context
I know that this is a bug and not an issue with my configuration because it worked before AND my configuration still works when I run the Studio locally. According to a comment on a separate bug fix, this bug was introduced a few weeks ago on the docker image.

Duplicate issue #11892: Self hosted studio always uses localhost:8000
Created: 2023-01-24T12:57:21Z
Bug report
Describe the bug
If you self host studio it always tries to use port 8000 regardless of the env variables you set.
This is the change that was supposed to fix something but also broke it.
To Reproduce

Self host studio
Observer requests in developer tab

Expected behavior
The values in .env should be used
System information

OS: fedora
docker: every docker image that was built after the mentioned commit

Closing comment (2023-01-25T21:04:33Z): Duplicate of #11656
Fix in progress in #11740
For a workaorund just build the docker image with the PR
Repository: supabase/supabase

Issue #18723: Ionic angular getting started doc is outdated
Created: 2023-11-04T16:16:35Z
Build a User Management App with Ionic Angular is outdated in many places. I'd really love to get started with supabase but the documentation being so outdated & not linked with local development which causes me to link everything together on my own is so frustrating as I started noticing things are outdated. Very very unfriendly to new users :(

Duplicate issue #13232: Ionic Vue tutorial is out of date
Created: 2023-03-27T11:50:44Z
Improve documentation
Link
Ionic Vue User Management app
The problem
The documentation isn't up to date with the latest Supabase version. With the example, I expected to get up and running with no extra work like debugging, etc etc. It has been a couple of days and I still haven't gotten it running unfortunately. :(
Improvements needed
There are many things that prevent this app from even starting.
Fixes needed in the doc
This shows an error, in App.vue
//Existing in App.vue
store.user = await supabase.auth.getUser() ?? {} 
//What I changed it to to make the error go away
store.user = (await supabase.auth.getSession()).data.session?.user ?? {}
This shows an error in Account.vue, apparently session doesn't exist?
<p>{{ session?.user?.email }}</p>
Got an error in Login.vue
//Existing
const { error } = await supabase.auth.signIn({ email: email.value })
//This fixed it
const { error } = await supabase.auth.signInWithOtp({ email: email.value })
Getting this error, not sure what to do
//Error
[Vue warn]: Component <App>: setup function returned a promise, but no <Suspense> boundary was found in the parent component tree. A component with async setup() must be nested in a <Suspense> in order to be rendered. 
  at <App>

//I tried this in App.vue, still not resolved
<template>
  <suspense>
    <ion-app>
      <suspense>
        <ion-router-outlet />
      </suspense>
    </ion-app>
  </suspense>
</template>
I'm stuck here:

Additional info needed in the doc

This file, /store isn't mentioned in the docs
In many sections like these, the file name isn't mentioned (I need to copy-paste this, but where?)

Closing comment (2024-01-23T10:02:45Z): related to #18723 and #17507
Repository: supertuxkart/stk-code

Issue #2169: Continuing a saved GP causes “last lap” sound to be played many times throughout the race (UPDATE: Bug may be caused by something else!)
Created: 2015-05-02T13:44:29Z
When I continue a saved GP, I will hear the “last lap” sound (or something similar, I am not sure) a lot of time again and again throughout the race.
This bug happens if you continue a saved grand prix. It seems only to happen after you have done so, I have never experienced the bug in other situations.
Also, this bug seems to continue for all future GP races (even non-GP) in the same STK session as well. If you restart STK, the sound weirdness is gone, until you continue a GP again.
Sometimes the sound in question is strangely distorted.
STK version: 0.9

Duplicate issue #2153: Race start sound repeat bug
Created: 2015-04-30T11:35:37Z
When you start up a race the sound of it starting before the actual race keeps repeating non stop for the whole entire race and is really annoying.

Closing comment (2017-02-03T20:59:18Z): Is this the same as #2169? Are you able to reproduce it under valgrind? This is certainly an issue in 0.9.2, though it never occured for me in git version.
Repository: supertuxkart/stk-code

Issue #235: City track, can drive on water
Created: 2014-02-24T23:40:12Z
Author: auria
This happened after I exported it again, and I didn't test before re-exporting, so maybe the problem is the blend only

Duplicate issue #305: Other crash at shutdown
Created: 2014-02-24T23:40:42Z
Author: auria
I ''think'' this is not the same as the others; sorry if it is a duplicate
#0  0x00248837 in Request::getCommand at request.hpp:84
#1  0x00247e32 in NetworkHttp::mainLoop at network_http.cpp:157

The request object is null. The logging is
[Requesting cancellation of download.
[addons](addons]) Inserting QUIT request.
[Cancelling network thread.
[addons](addons]) Cancelled network thread. Return code: 0

Closing comment (2014-02-24T23:49:08Z): Author: hikerstk
grin This looks like a duplicate of #235, which should be fixed in r8700.
Thanks for the report!
Joerg
Repository: supertuxkart/stk-code

Issue #2885: There is something wrong with normal maps
Created: 2017-07-23T14:26:51Z
I did some test of normal map on simple objects and the results are strange.
When you enable normal maps it looks like part where you have the UV seams are set to hard.
Here is an example, same mesh, same parameters with/without normal map enabled

And without normal map

At first I thought there was something wrong with the mesh, but after looking in blender, the mesh is displayed without any issues

Duplicate issue #2243: Track making: Normal Maps not displayed correctly
Created: 2015-07-17T16:12:52Z
I'm trying to use normal maps in my track but they don't work properly (See attached image). I'm adding normal maps in the image properties of the texture and they're working so far.
What I've done:

Making the mesh where the normal map should apply a seperate object.
Tried with a second UV-Layer with the normal map.
Changing the size of the textures.
Checked normals and mesh.
Changed sun position (which doesn't affect the position of this strange line on the picture).

As I don't see any mistake on my side so far -> I suppose it's just a bug.

Closing comment (2017-11-08T06:15:18Z): Actually it's duplicate of #2885 and can be fixed in 0.9.4
Repository: supertuxkart/stk-code

Issue #1188: Add way to re-watch cutscenes
Created: 2014-02-24T23:46:43Z
Author: auria
Add a way to re-watch the intro cutscene, requested on the forum
Migrated-From: https://sourceforge.net/apps/trac/supertuxkart/ticket/1132

Duplicate issue #5265: Give user the option to play animation video more than once
Created: 2025-01-23T18:03:29Z
When starting story mode for the first time you get to see an animation video.
But after the first time it does not appear there is any way to replay it from within the game.
config-0.10/players.xml have first-time attribute to edit manually to see the animation video again:
  <story-mode first-time="true"

Maybe in story mode when you drive the kart and press Esc there could be a "Replay introduction" or whatever to see the animation video again.
And in Help > Story Mode there about be a button to play the animation video. Just like there is a button in General to play the tutorial again.
At the place you start with the kart there is a spot to play the tutorial. It does not appear on the minimap.
Maybe a similar spot could be added near the beginning.
The first time you drive into the open garage the game pauses.
Maybe something could be added in the closed garage to play the animation video if its not used for anything.

Closing comment (2025-01-23T18:07:45Z): Duplicate of #1188
Repository: supertuxkart/stk-code

Issue #2838: Nitro sound only plays when pressing the key
Created: 2017-04-16T18:44:42Z
The nitro sound plays only when the key for using nitro is pressed, but if you press the button only short, nitro is used for a longer time without the sound.
The sound should be played when nitro is used (and not only when the button is pressed).

Duplicate issue #3033: Using Nitro while airborne uses the nitro but has no effect.
Created: 2017-11-10T21:15:39Z
Not even the nitro trails happen.

Closing comment (2017-11-11T20:41:27Z): Not the same, but somehow related to #2838 (just for reference).
Repository: supertuxkart/stk-code

Issue #4356: Incorrect Follow the Leader loss
Created: 2020-08-26T16:57:09Z
The "cannon" in Cornfield Crossing is causing position interpolation issues, the game thought I was last while i was not, as the counter expired and I was inside the "cannon".
Tagging as minor because FTL is the game's most useless mode.

Duplicate issue #4517: Karts in mid-jump are eliminated from Follow The Leader
Created: 2021-04-09T19:11:55Z
Description
Problem: When a kart is in mid-jump in a Follow The Leader competition, the kart is eliminated, regardless of their position in the race.
Steps to reproduce

Start a Follow The Leader competition with multiple AI-controlled karts.
Select Cornfield Crossing track as the race location.
On the opening lap, move into the middle of the pack and hit the jump into the barn when the elimination timer reaches zero.
The player is removed, regardless of their position in the field. possibly because they are not technical on the track.

Configuration
STK release version:  1.0
STK Source (PPA, distribution package, official binary, etc.): Debian Stable repository.
System: Linux (x86_64)
Graphics card: AMD Radeon HD 6410D
CPU: Dual-core 2.8GHz AMD 64-bit

Closing comment (2021-09-08T13:21:14Z): Actually this is a duplicate of #4356
Closing this, use the other issue for further discussion.
Repository: supertuxkart/stk-code

Issue #1333: Fort Magma cups
Created: 2014-05-17T17:13:44Z
Hi,
I have won bronze cup in Fort Magma and finished the game. Then I won some other races and went back to Fort Magma. When I won silver cup, the game didnt show up anything about that I finished the challenge (like for other races), but the race is saved with silver cup. The same with gold cup, when I finish challenge, I can "restart" race even in the case I have won (it's a bit confusing, I dont know if finished challenge or not until I leave the race and look at map). All other races are OK!
Version: 0.8.1-2

Duplicate issue #3572: No unlock screen after defeating Nolok in Fort Magma in Story Mode
Created: 2018-11-15T14:14:05Z
Description
There's no unlock screen after defeating Nolok on Fort Magma in Story Mode.
Since this challenge unlocks quite a few things, I think the unlock screen should not be skipped.
Steps to reproduce

Play Story Mode
Defeat Nolok in Fort Magma for the first time

Suggested fix
I suggest that the following things should happen after you beat Nolok:

Play the cut scene “Gnu gets freed”
Show the unlock screen
Roll credits

Configuration
STK release version: 0.9.2

Closing comment (2018-11-16T22:06:09Z): Related to #1333
Repository: supertuxkart/stk-code

Issue #253: Handling old URLs for download manager
Created: 2014-02-24T23:40:19Z
Author: hikerstk
If an old (invalid) url is given, and the url can not be found, try the default URL first before going into error state.
Minor priority, since it should only affect people who tried the very very old download manager.
Additionally, we might put a redirect news file at the old url.

Duplicate issue #323: Missing lapline
Created: 2014-02-24T23:40:50Z
Author: auria
bovineuniversity reported on the forum that the island lapline tends to be not counted when you don't drive directly on it

Closing comment (2014-02-24T23:49:17Z): Author: hikerstk
Since island track has no shortcut this is not a duplicate of #253.
The only explanation for this bug is if the kart is driving so far left of the start line, that it is (in 2d projection onto the plan) closer to the quads 'after the loop' (further uphill). In this case the kart would be considered to be on that part of the track, and therefore not trigger a new lap. I tried to reproduce this, but I wasn't able to do it: the hills to the left are steep enough. With a lot of nitro I was able to drive uphill far enough to reach the upper part of the track, but it was very obvious that I was not crossing the finish line (and if this was the case I would say not to fix this, since you should actually cross the finish line imho).
We could change the track design by moving the start line back so that there is no other road close by (funnily enough that would probably to the location where the start line was originally, before it was moved in order to allow more karts to start on this track, i.e. before we had the algorithm for kart placement).
Since lap lines have their own disadvantage (there might be a few frames in which the order is not exact), I would prefer not add a lapline here, but instead try to find the real reason for this behaviour (since it might affect other tracks as well): if this issue happen, immediately press F10, and email/attach the (compressed) history.dat file. This will allow us to reproduce what was happening.
Then we can decide if we want to alter the track, or fix a bug.
I wouldn't consider this a release blocker (unless someone can reproduce it), so I'll assign it to "can't reproduce", but if we get enough information to reproduce it will fix it before 0.7.2.
Thanks for the report!
Joerg
Repository: supertuxkart/stk-code

Issue #3779: Rescue sometimes place the kart just in front of a banana
Created: 2019-03-01T15:29:19Z
In some tracks, there is a banana right in the middle of the road. This by itself is not an issue, but rescue is completely unaware of any track elements besides the drivegraphs, so when being rescued in some spots, the kart will be placed right in front of the banana,with no way to avoid it besides going backwards for a moment before re-acceleration.
Expected behavior : the rescue placement is made aware of bananas (and chewing gums ?) and avoid placing the kart right in front of them.
Related possibility to consider : give a short immunity after rescue.

Duplicate issue #3846: Rescue point in reverse Ravenbridge Mansion respawns you on banana
Created: 2019-04-16T13:26:45Z
https://satoshiupload.com/images/dNfmeckA7y.jpg
If you drive Ravenbridge Mansion in reverse mode and you reset behind the banana in above screenshot, you will respawn on the banana and collect it immediately.
The banana is on the big curvy cobblestone serpentines that lead up to the road, 2nd level.

Closing comment (2019-04-16T13:59:32Z): Duplicate of #3779
Repository: sveltejs/kit

Issue #9817: Print filepaths using Svelte or SvelteKit-specific code in @sveltejs/package
Created: 2023-05-02T14:43:08Z
Describe the problem
svelte-package warns you when you include a Svelte-specific or SvelteKit-specific import in your package but do not include it in dependencies or peerDependencies. If not including dependencies or peerDependencies was intentional, finding the file that uses the wrong import takes a minute.
Describe the proposed solution
It would be helpful if svelte-package printed the file in the terminal. Preferably with a link you can Ctrl+Click in VS Code to jump to the file immediately.
Alternatives considered
No response
Importance
would make my life easier
Additional Information
No response

Duplicate issue #10150: Provide more specific details about SvelteKit-specific imports
Created: 2023-06-13T06:04:01Z
Describe the problem
When running pnpm build, the following message is displayed after a successful build:
@sveltejs/package found the following issues while packaging your library:
You are using SvelteKit-specific imports in your code, but you have not declared a dependency on `@sveltejs/kit` in your `package.json`. Add it to your `dependencies` or `peerDependencies`.

This message is rather vague and hard to debug. It would be helpful if the message could provide more specific details about the files and/or line numbers where the SvelteKit-specific imports are being used.
Describe the proposed solution
pnpm build

Alternatives considered
No response
Importance
would make my life easier
Additional Information
n/a

Closing comment (2023-06-13T15:10:15Z): Closing as duplicate of #9817
Repository: sveltejs/kit

Issue #9674: ISR revalidatePath, revalidateAll, revalidateTag
Created: 2023-04-15T13:55:42Z
Describe the problem
Currently the way to force the revalidation of an ISR page is to query the server like this:

GET or HEAD request with x-prerender-revalidate: <token> will force the asset to be re-validated

I have some data that is displayed on all pages of my website, and would like to invalidate all pages when the data is updated. Currently I workaround this issue by redeploying the app, but as this is done frequently I'm interested in a quicker ISR cache invalidation instead.
Describe the proposed solution
The revalidatePath from NextJS would solve my issue  assuming I can revalidateAll = () => revalidatePath('/'). NextJS also proposes revalidating by tag using revalidateTag.
Importance
nice to have

Duplicate issue #10365: invaildateAll equivalent for ISR
Created: 2023-07-11T04:53:21Z
Describe the problem
I have a use case where a user can publish large sets of changes to data that’s used throughout a public facing app (a portfolio platform), and these changes happen infrequently, making the app a perfect use-case for non-expiring ISR that is revalidated when a user publishes changes. Sort of like a static site that rebuilds on the fly.
However revalidating every path where any of the changed data could appear indvidually (with a x-prerender-revalidate: <token> request) is non-trivial and would be prone to error
Describe the proposed solution
I would love to have a rough equivalent of invalidateAll, where I could revalidate an entire ISR cache every time a user publishes data so I can be sure their portfolio isn't stale.
I haven't thought through a possible API much, but first thing that comes to mind is to just borrow from invalidate with an x-prerender-revalidate-all: <token> to / or similar.
Alternatives considered
Looping through every URL path that could be impacted and sending revalidation requests to each. Fragile and cumbersome, but possbile.
Importance
would make my life easier
Additional Information
No response

Closing comment (2023-09-09T14:55:49Z): Similar to #9674
Repository: sveltejs/kit

Issue #924: ssr: false - Breaks all styling
Created: 2021-04-07T22:41:56Z
Describe the bug
Styling seems to break when npm run build && npm start with ssr: false.
npm start dev appears to be fine.
To Reproduce
npm init svelte@next
ssr: false in svelte.config.cjs
npm run build && npm start

The output of npx envinfo --system --npmPackages svelte,@sveltejs/kit,vite --binaries --browsers

  System:
    OS: macOS 11.2.2
    CPU: (8) arm64 Apple M1
    Memory: 373.28 MB / 8.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 15.12.0 - /opt/homebrew/bin/node
    npm: 7.6.3 - /opt/homebrew/bin/npm
  Browsers:
    Firefox: 87.0
    Safari: 14.0.3
    Safari Technology Preview: 14.2
  npmPackages:
    @sveltejs/kit: next => 1.0.0-next.71 
    svelte: ^3.29.0 => 3.37.0 
    vite: ^2.1.0 => 2.1.5 


Your browser
Firefox
Your adapter (e.g. Node, static, Vercel, Begin, etc...)
Tested on node & static


Severity
How severe an issue is this bug to you? Is this annoying, blocking some users, blocking an upgrade or blocking your usage of SvelteKit entirely?
Production builds appear to be blocked for users not using ssr

Duplicate issue #888: Disable SSR for specific pages/routes on production
Created: 2021-04-05T14:46:00Z
Disabling SSR for specific routes doesn't works on production.
only at /routes/account/index.svelte:
<script context="module">
	export const ssr = false;
</script>


Locally works fine. However, when running the node server, accessing the /account page it won't work properly. Css's is not loaded
You can check an example page here: https://www.imobcorreia.com.br/test
Severity
annoying

Closing comment (2021-07-25T08:21:40Z): Closing as this was reported to be related to #924 which is fixed now
Repository: sveltejs/kit

Issue #754: True SPA mode
Created: 2021-03-29T16:43:45Z
We now have the ssr: false option which gives us something close to SPA mode: https://kit.svelte.dev/docs#ssr-and-javascript
It doesn't get us all the way there though, because in a typical SPA you would likely want to generate a single fallback page that handles all requests — for example Surge lets you add a 200.html file, while Netlify allows you to add something like this to _redirects:
/*    /200.html   200

By contrast, SvelteKit expects to generate (whether at runtime or prerender time) an HTML page that includes no content, but does include information about the route that should be hydrated, since the router isn't invoked on load. To create a true SPA, SvelteKit needs to create a content-less file that doesn't contain any route information, and the router needs to figure out what JS to load and execute.
I'm not certain how best to do this in a provider-agnostic way.

Duplicate issue #1172: How to build/export $error.svelte / 404 page with adapter-static ?
Created: 2021-04-22T14:45:31Z
After running npm run build with adapter-static I hoped that the $error.svelte page would be generated as well. When statically hosted and whenever a non-existent route is hit, Sveltkit would redirect to the 404.html page.
With Sapper we just added to package.json a couple of lines
"build:export": "sapper export --entry \"/ /404\"",
"postexport": "mv __sapper__/export/404/index.html __sapper__/export/404.html"
I wonder how it is done with Sveltekit. Thanks

Closing comment (2021-04-23T06:29:44Z): This is highly related to #754 and possibly a duplicate of that issue

Thanks for pointing it out. I believe it is a duplicate indeed. Hopefully, the fallback feature will be implemented soon.
Repository: sveltejs/kit

Issue #2576: Add typescript version of svelte.config.js
Created: 2021-10-09T20:04:24Z
Describe the problem
In the FAQ, it is said I can add a middleware in dev mode by creating a vite plugin.
But my middleware is a typescript  file and I cannot import it into my svelte.config.js.
I tried to rename svelte.config.js to svelte.config.ts but got an error "Cannot find module 'C:\Users\JEROME\Documents\MesDeveloppements\SitesInternet\tarteen\svelte.config.cjs'".
Describe the proposed solution
Allow svelte config file to be written in typescript.
Alternatives considered
Don't see any
Importance
would make my life easier
Additional Information
No response

Duplicate issue #12942: `svelte.config.ts` not recognized
Created: 2024-11-03T13:54:36Z
Describe the bug
Bun can natively import TS files without any plugin needed. However, renaming svelte.config.js to svelte.config.ts makes the build (or dev server) fail.
Reproduction
mv svelte.config.js svelte.config.ts
Logs
The logs contain import failures mentioning my project files which I don't disclose (but does not mention import failure of `svelte.config.ts`).
System Info
Running using Bun in Docker.

  System:
    OS: Linux 6.11 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
    Container: Yes
    Shell: 5.1.4 - /bin/bash
  Binaries:
    bun: 1.1.34 - /tmp/bun-node-5e5e7c60f/bun
  npmPackages:
    @sveltejs/adapter-node: ^5.2.8 => 5.2.9
    @sveltejs/enhanced-img: ^0.3.9 => 0.3.9
    @sveltejs/kit: ^2.7.2 => 2.7.2
    @sveltejs/vite-plugin-svelte: ^4.0.0 => 4.0.0
    svelte: ^5.0.5 => 5.0.5
    vite: ^5.4.9 => 5.4.9
Severity
annoyance
Additional Information
No response

Closing comment (2024-11-03T14:02:42Z): Duplicate of #2576
Repository: sveltejs/sapper

Issue #948: Make layout know if it's in error page or home page
Created: 2019-10-20T06:38:24Z
Is your feature request related to a problem? Please describe.
I asked this question on SO, but doesn't get much attentions.
I want to style the page differently in home and error page, but segment is undefined in both pagas.
Describe the solution you'd like
Either make segment return different values (e.g., "" vs undefined), or another variable saying if the current is error or not.
I lean toward the former.
How important is this feature to you?
Giving different layouts to home and error page layout is pretty common I think, and given there doesn't seem to be a workaround, I feel it's pretty important.

Duplicate issue #1343: segment is undefined client side on error page
Created: 2020-07-27T17:20:59Z
Describe the bug
A clear and concise description of what the bug is.
The segment variable is undefined on client side (defined on server side)  in the _layout.svelte file when rendering the _error.svelte file
Logs
Please include browser console and server logs around the time this bug occurred.
To Reproduce
To help us help you, if you've found a bug please consider the following:
Run sapper starter template and navigate to /a with the following code in _layout.svelte
export let segment;
console.log(segment) // ssr: "a", client: undefined


If possible, we recommend creating a small repo that illustrates the problem.
Reproductions should be small, self-contained, correct examples – http://sscce.org.

Occasionally, this won't be possible, and that's fine – we still appreciate you raising the issue. But please understand that Svelte is run by unpaid volunteers in their free time, and issues that follow these instructions will get fixed faster.
Expected behavior
A clear and concise description of what you expected to happen.
Client side segment should have the same value as the server side
Stacktraces
If you have a stack trace to include, we recommend putting inside a <details> block for the sake of the thread's readability:

  Stack trace
Stack trace goes here...

Information about your Sapper Installation:


Your browser and the version: (e.x. Chrome 52.1, Firefox 48.0, IE 10)


Your operating system: (e.x. OS X 10, Ubuntu Linux 19.10, Windows XP, etc)


Your hosting environment: (i.e. Local, GCP, AWS, Now, etc...)


Sapper version (Please check you can reproduce the issue with the latest release!)


Svelte version (Please check you can reproduce the issue with the latest release!)


If it is an exported (npm run export) or dynamic application.


Whether your application uses Webpack or Rollup


Severity
How severe an issue is this bug to you? Is this annoying, blocking some users, blocking an upgrade or blocking your usage of Sapper entirely?
Note: the more honest and specific you are here the more we will take you seriously.
Additional context
Add any other context about the problem here.

Closing comment (2020-07-27T17:34:46Z): Approximately a duplicate of #948 and a few other related issues.
Repository: sveltejs/sapper

Issue #1040: Best way for patching goto()? Unsaved data // onbeforeunload logic
Created: 2019-12-31T20:37:07Z
Hey Sapper Community ❤️
I do:
async function gotoURL(...args) {
	if (isFormUnsaved === true){
		if (window.confirm("Are we leaving already?") === false){
			return false;
		}
	}
	return await goto(...args);
}
And it works for on:click.
How can I "patch" goto, for real links <a href="/somewhere">Meow</a>

Duplicate issue #1035: How to make a validation alert before navigating to another page ?
Created: 2019-12-25T20:10:58Z
i've been looking for something like beforeDestroy to create validation when user has not fill the form completely and they want to navigate to another page they should receive alert like "are you sure want to discard your changes ?", is there any possible way to create that validation on sapper ?

Closing comment (2020-01-03T12:01:22Z): This is a question, and a duplicate of #1040 as mentioned by 0xsven. Please ask questions in the discord
Repository: sveltejs/sapper

Issue #952: Feature Request: Hydratable {#await} blocks
Created: 2019-10-21T16:20:51Z
Is your feature request related to a problem? Please describe.
When using {#await}, Sapper doesn't seem to wait at all for the result of the promise, and always renders the the placeholder part.
In the below example, Hello darkness. initially appears on the page, and is then replaced by Hello world., potentially confusing the visitor.
Hello
{#await Promise.resolve("world")}
  darkness.
{:then result}
  {result}.
{/await}

Describe the solution you'd like
It would be amazing if Sapper was able to resolve the promises server-side so that the browser doesn't even need to execute them again.
I'm currently thinking how this behavior could be implemented, or an elegant work-around. No ideas so far...

Duplicate issue #1177: SSR and GraphQL: how to avoid the loading state if no javascript is present (async calls rendering)?
Created: 2020-05-01T17:01:24Z
I'm trying Sapper and SSR (server-side-rendering) for the first time today.
I need to use it with NO-Javascript browsers along with standard ones.
In my Svelte/Sapper app I'm using GraphQL (Apollo, URQL or SVQL doesn't matter).
QUESTION
Whatever the GraphQL client I choose I can't understand how to manage the loading of the call to the GraphQL endpoint.
I mean that since we are not in an environment where I can use the reactivity to an event to rewrite part of the DOM (I am rendering in the nodejs server) every time a user (or a bot: search engine) browses the site (without javascript) will only see the wait state for the GraphQL call: "Loading todos ...".
Am I brutally wrong?
CODE EXAMPLE
<script>
  import { initClient, query } from '@urql/svelte';

  initClient({ url: "https://0ufyz.sse.codesandbox.io" });

  const todos = query({
    query: `
      query {
        todos {
          id
          text
          complete
        }
      }
    `
  });
</script>

{#if $todos.fetching} <!-- This is the only state I see in my server rendered response -->
  Loading todos...
{:else}
  <ul>
    {#each $todos.data.todos as todo}
      <li>{todo.text}</li>
    {/each}
  </ul>
{/if}
Even if I manage to wait for the GraphQL response in the express server and to render the data instead of the loading message, the problem is that the times are much longer (if the GraphQL endpoint is slow) and the user experience is depressing, especially for the standard user with the browser and javascript.
Maybe I am missing something in the reasoning.
But what?
UPDATE
Great guys at Routify use something called $ready() (https://routify.dev/docs/helpers#ready) to handle async calls.
I don't know what is wrong with me or if there is already something in Sapper to handle this case.
Maybe we can "differentiate" usesrs base on some headers values.
Can you point me in the right direction on this? I read all the Sapper docs!

Closing comment (2020-05-01T17:01:35Z): Maybe related to #952?
Repository: sveltejs/sapper

Issue #30: Hooks
Created: 2017-12-19T22:57:09Z
Saying you wanted to show a loading indicator when navigating between routes, or something of that nature — the best way to do that would be to have a navigation hook:
import { onnavigate } from 'svelte/runtime/app';

onnavigate((from, to, promise) => {
  console.log(`navigating from ${from.href} to ${to.href}`);
  const loading = new LoadingIndicator();
  promise.then(loading.destroy);
});
Need to consider what the arguments should be. Is there a possibility of something like onprogress, for example? Should from and to just be hrefs, or should we also get params etc? Should it be possible to cancel the navigation, or change it, or inject some data (e.g. {slidingTo: 'left'}), or delay it pending some operation?
And should it be onnavigate(...), or on('navigate', ...)? i.e. do we anticipate adding more events?

Duplicate issue #74: Equivalent of onload for Sapper-loaded pages
Created: 2018-01-08T09:42:08Z
Is there an easy event handler for when Sapper navigates to and loads a page?
For my particular use case, I'm lazy loading images and swapping a blurry image src with a more detailed image src after the document has loaded. This works great using window.onload when I initially navigate to the page or hard refresh, but when navigating from another page within my Sapper app, the onload method is never called. Is there a Sapper equivalent for onload?

Closing comment (2018-01-08T09:54:14Z): That's exactly it - thanks! I'll close this issue as it's a duplicate of #30.
Repository: sveltejs/sapper

Issue #1488: Export does not bail on error
Created: 2020-09-05T20:39:31Z
Describe the bug
I'm exporting my sapper site and intentionally throwing errors in the pages. When export runs all of my pages return a 500 error. Instead of failing on error, the export process seems to continue processing all of the failing pages then report that the export was a success. It would make more sense to me to have export fail if an error is encountered to avoid "successfully" building a broken site.
Logs
Error: FAIL
    at getStuff (/Users/code/__sapper__/build/server/server.js:41:9)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async get (/Users/code/__sapper__/build/server/server.js:247:23)
    at async handle_route (/Users/code/__sapper__/build/server/server.js:1266:5)
   2.45 kB   (500) page-1/index.html
> Finished in 7.0s. Type npx serve __sapper__/export to run the app.
✨  Done in 7.14s.

To Reproduce
Instructions in the bug description
Severity
Medium. My website builds on a cron and one of my data sources is flaky (for several hours at a time). I need to be able to skip that cron run when the website export failed.

Duplicate issue #870: Flag to fail `sapper export` if it finds a 500 / 404
Created: 2019-09-03T20:24:28Z
Is your feature request related to a problem? Please describe.
When you execute sapper export it will crawl the entire website and, if it finds a missing page or can't execute something, will export a matching 500 or 404 for a given path.  This is shown in red on the console and a developer looking at this will almost certainly spot the issue and go fix it.
The problem is when this is part of an automated build and doesn't get developer eyeballs.  sapper export still returns a success code and the entire build is marked as a complete, even though there is almost certainly an issue that needs to be fixed.
Describe the solution you'd like
There should be a flag added to sapper export so that, if it encounters an error on any page, it will exit with an error code.
How important is this feature to you?
This is quality of life improvement.  Sufficient levels of automated testing would accomplish the same thing.

Closing comment (2021-02-01T09:21:34Z): +1. Also found a possible duplicate: #1488
Repository: swiftlang/swift-testing

Issue #162: Value not shown in error message when an expectation condition has effects (try/await)
Created: 2023-12-15T15:23:27Z
Description
#expect works differently when await keyword is inside its body. await #expect(expr) shows a breakdown of the actual value, while #expect(await expr) does not. I would like to know why the expectation failed even if the result is computed from an async expression.

Expected behavior
#expect(await Array(stream) == [1,2]) throws the error testAll(): Expectation failed: (Array(stream) → [1, 2, 3]) == ([1,2] → [1, 2])
Actual behavior
#expect(await Array(stream) == [1,2]) throws the error testAll(): Expectation failed: await Array(stream) == [1,2]
Steps to reproduce
No response
swift-testing version/commit hash
3fa4ea0
Swift & OS version (output of swift --version && uname -a)
swift-driver version: 1.87.3 Apple Swift version 5.9.2 (swiftlang-5.9.2.2.56 clang-1500.1.0.2.5)
Target: arm64-apple-macosx14.0
Darwin MBP 23.1.0 Darwin Kernel Version 23.1.0: Mon Oct  9 21:27:24 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6000 arm64

Duplicate issue #606: Value not shown when calling function in #expect
Created: 2024-08-08T01:03:35Z
Description
When the following expectation fails:
let sample = try tile.sample(atX: 0, y: 0)
#expect(sample.isApproximatelyEqual(to: 10.276871, absoluteTolerance: 0.0001))
the message printed is
Expectation failed: (sample → 455.85916).isApproximatelyEqual(to: 10.276871, absoluteTolerance: 0.0001)

But if the expectation is written like this:
#expect(try tile.sample(atX: 0, y: 0).isApproximatelyEqual(to: 10.276871, absoluteTolerance: 0.0001))
The message doesn't include the value:
Expectation failed: try tile.sample(atX: 0, y: 0).isApproximatelyEqual(to: 10.276871, absoluteTolerance: 0.0001)

Would be nice if it showed the value in that case too.
Expected behavior
Show the value regardless of the expression.
Actual behavior
No response
Steps to reproduce
No response
swift-testing version/commit hash
a62bf99
Swift & OS version (output of swift --version ; uname -a)
% swift --version ; uname -a
swift-driver version: 1.113 Apple Swift version 6.0 (swiftlang-6.0.0.7.6 clang-1600.0.24.1)
Target: arm64-apple-macosx14.0
Darwin eclipsem1.local 23.5.0 Darwin Kernel Version 23.5.0: Wed May  1 20:12:58 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6000 arm64

Closing comment (2024-08-08T01:14:00Z): Duplicate of #162