Remove /next from docs URLs

apps/reference/docs/architecture.mdx

@@ -35,5 +35,5 @@ Most notably, we use Postgres rather than a NoSQL store. This choice was deliber
 | Auth                       | SvelteKit Auth Helpers | Alpha | [Link](/docs/guides/auth/auth-helpers/sveltekit) |
 | Public API                 |                        | Beta  | [Link](/docs/reference/api)                      |
 | CLI                        |                        | Beta  | [Link](/docs/guides/cli)                         |
-| Client Library: JavaScript |                        | GA    | [Link](/docs/reference/javascript/next/)         |
+| Client Library: JavaScript |                        | GA    | [Link](/docs/reference/javascript)               |
 | Client Library: Dart       |                        | Beta  | [Link](/docs/reference/dart)                     |

apps/reference/docs/guides/auth/auth-helpers/auth-ui.mdx

@@ -18,7 +18,7 @@ It supports custom themes and extensible styles to match your brand and aestheti
 
 ## Set up Auth UI
 
-Install the latest version of [supabase-js](/docs/reference/javascript/next/) and the Auth UI package:
+Install the latest version of [supabase-js](/docs/reference/javascript) and the Auth UI package:
 
 ```bash
 npm install @supabase/supabase-js@rc @supabase/auth-ui-react

apps/reference/docs/guides/storage-cdn.mdx

@@ -19,7 +19,7 @@ Aside from performance, CDNs also help with security and availability by mitigat
 
 By default, assets are cached both in the CDN and in the user’s browser for 1 hour. After this, the CDN nodes ping the storage server to see if an object has been updated.
 
-You can modify this cache time when you are [uploading](https://supabase.com/docs/reference/javascript/next/storage-from-upload) or [updating](https://supabase.com/docs/reference/javascript/next/storage-from-update) an object by modifying the `cacheControl` parameter.
+You can modify this cache time when you are [uploading](https://supabase.com/docs/reference/javascript/storage-from-upload) or [updating](https://supabase.com/docs/reference/javascript/storage-from-update) an object by modifying the `cacheControl` parameter.
 
 If you expect the object to not change at a given URL, setting a longer cache duration is preferable.
 

apps/reference/docs/guides/storage.mdx

@@ -272,7 +272,7 @@ You can access the storage API directly with the same endpoint. See the <a href=
 
 Supabase Storage is integrated with your [Postgres Database](/docs/guides/database).
 This means that you can use the same [Row Level Security Policies](/docs/guides/auth#policies)
-for managing access to your files. Supabase Storage stores metadata in the `objects` and `buckets` table in the storage schema. To allow read access to files, the RLS policy must allow users to `SELECT` the `objects` table and for uploading a new object, the RLS policy must grant users access to `INSERT` into the `objects` table and so on. The mapping between the different API calls and the database permissions required is documented in the [Reference docs](/docs/reference/javascript/next/storage-createbucket).
+for managing access to your files. Supabase Storage stores metadata in the `objects` and `buckets` table in the storage schema. To allow read access to files, the RLS policy must allow users to `SELECT` the `objects` table and for uploading a new object, the RLS policy must grant users access to `INSERT` into the `objects` table and so on. The mapping between the different API calls and the database permissions required is documented in the [Reference docs](/docs/reference/javascript/storage-createbucket).
 
 :::note
 

apps/www/_blog/2022-08-16-supabase-js-v2.mdx

@@ -302,7 +302,7 @@ Update today by running:
 npm i @supabase/supabase-js@rc
 ```
 
-You can find a full list of updates, breaking changes, and a migration guide in our [Release Notes](https://supabase.com/docs/reference/javascript/next/release-notes).
+You can find a full list of updates, breaking changes, and a migration guide in our [Release Notes](https://supabase.com/docs/reference/javascript/release-notes).
 
 We'll continuing merging security fixes to v1, with maintenance patches for the next three months.
 
@@ -321,8 +321,8 @@ We'll continuing merging security fixes to v1, with maintenance patches for the
 
 ## Links
 
-- [v2 Release Candidate Documentation](https://supabase.com/docs/reference/javascript/next)
-- [Release Notes & Migration Guide](https://supabase.com/docs/reference/javascript/next/release-notes)
+- [v2 Release Candidate Documentation](https://supabase.com/docs/reference/javascript)
+- [Release Notes & Migration Guide](https://supabase.com/docs/reference/javascript/release-notes)
 
   ## More Launch Week 5
 

apps/www/components/LaunchWeek/days.json

@@ -43,12 +43,12 @@
         "products": [
           {
             "title": "Supabase.js v2 Docs",
-            "url": "/docs/reference/javascript/next/installing",
+            "url": "/docs/reference/javascript/installing",
             "description": "Updated documentation for supabase-js"
           },
           {
             "title": "Typescript support",
-            "url": "/docs/reference/javascript/next/typescript-support",
+            "url": "/docs/reference/javascript/typescript-support",
             "description": "Using types generated directly from your database."
           }
         ]

apps/www/lib/redirects.js

@@ -1316,7 +1316,7 @@ module.exports = [
   {
     permanent: true,
     source: '/docs/reference/javascript/next/migration-guide',
-    destination: '/docs/reference/javascript/next/release-notes',
+    destination: '/docs/reference/javascript/release-notes',
   },
   {
     permanent: true,

spec/enrichments/tsdoc_v2/combined.json

@@ -63702,7 +63702,7 @@
               "kindString": "Type parameter",
               "flags": {},
               "comment": {
-                "shortText": "Types for the schema from the [type\ngenerator](https://supabase.com/docs/reference/javascript/next/typescript-support)\n"
+                "shortText": "Types for the schema from the [type\ngenerator](https://supabase.com/docs/reference/javascript/typescript-support)\n"
               },
               "default": {
                 "type": "intrinsic",

spec/enrichments/tsdoc_v2/postgrest.json

@@ -1717,7 +1717,7 @@
           "kindString": "Type parameter",
           "flags": {},
           "comment": {
-            "shortText": "Types for the schema from the [type\ngenerator](https://supabase.com/docs/reference/javascript/next/typescript-support)\n"
+            "shortText": "Types for the schema from the [type\ngenerator](https://supabase.com/docs/reference/javascript/typescript-support)\n"
           },
           "default": {
             "type": "intrinsic",

spec/enrichments/tsdoc_v2/postgrest_dereferenced.json

@@ -1792,7 +1792,7 @@
           "kindString": "Type parameter",
           "flags": {},
           "comment": {
-            "shortText": "Types for the schema from the [type\ngenerator](https://supabase.com/docs/reference/javascript/next/typescript-support)\n"
+            "shortText": "Types for the schema from the [type\ngenerator](https://supabase.com/docs/reference/javascript/typescript-support)\n"
           },
           "default": {
             "type": "intrinsic",

spec/supabase_js_v2.yml

@@ -93,7 +93,7 @@ pages:
       - If signUp() is called for an existing confirmed user:
           - If **Confirm email** is enabled in [your project](https://app.supabase.com/project/_/auth/settings), an obfuscated/fake user object is returned.
           - If **Confirm email** is disabled, the error message, `User already registered` is returned.
-      - To fetch the currently logged-in user, refer to [`getUser()`](/docs/reference/javascript/next/auth-getuser).
+      - To fetch the currently logged-in user, refer to [`getUser()`](/docs/reference/javascript/auth-getuser).
     examples:
       - name: Sign up.
         isSpotlight: true
@@ -641,8 +641,8 @@ pages:
     $ref: '@supabase/postgrest-js.PostgrestQueryBuilder.select'
     notes: |
       - By default, Supabase projects return a maximum of 1,000 rows. This setting can be changed in your project's [API settings](https://app.supabase.com/project/_/settings/api). It's recommended that you keep it low to limit the payload size of accidental or malicious requests. You can use `range()` queries to paginate through your data.
-      - `select()` can be combined with [Filters](/docs/reference/javascript/next/using-filters)
-      - `select()` can be combined with [Modifiers](/docs/reference/javascript/next/using-modifiers)
+      - `select()` can be combined with [Filters](/docs/reference/javascript/using-filters)
+      - `select()` can be combined with [Modifiers](/docs/reference/javascript/using-modifiers)
       - `apikey` is a reserved keyword if you're using the [Supabase Platform](/docs/guides/hosting/platform) and should be avoided as a column name](https://github.com/supabase/supabase/issues/5465).
     examples:
       - name: Getting your data
@@ -1088,7 +1088,7 @@ pages:
       - name: Querying with count option
         description: |
           You can get the number of rows by using the
-          [count](/docs/reference/javascript/next/select#parameters) option. For
+          [count](/docs/reference/javascript/select#parameters) option. For
           example, to get the table count without returning all rows:
 
           <Tabs>
@@ -1367,7 +1367,7 @@ pages:
     title: 'Modify data: update()'
     $ref: '@supabase/postgrest-js.PostgrestQueryBuilder.update'
     notes: |
-      - `update()` should always be combined with [Filters](/docs/reference/javascript/next/using-filters) to target the item(s) you wish to update.
+      - `update()` should always be combined with [Filters](/docs/reference/javascript/using-filters) to target the item(s) you wish to update.
     examples:
       - name: Updating your data
         description: |
@@ -1758,7 +1758,7 @@ pages:
     title: 'Delete data: delete()'
     $ref: '@supabase/postgrest-js.PostgrestQueryBuilder.delete'
     notes: |
-      - `delete()` should always be combined with [filters](/docs/reference/javascript/next/using-filters) to target the item(s) you wish to delete.
+      - `delete()` should always be combined with [filters](/docs/reference/javascript/using-filters) to target the item(s) you wish to delete.
       - If you use `delete()` with filters and you have
         [RLS](/docs/learn/auth-deep-dive/auth-row-level-security) enabled, only
         rows visible through `SELECT` policies are deleted. Note that by default
@@ -1958,8 +1958,8 @@ pages:
       - name: Call a Postgres function with filters
         description: |
           Postgres functions that return tables can also be combined with
-          [Filters](/docs/reference/javascript/next/using-filters) and
-          [Modifiers](/docs/reference/javascript/next/using-modifiers).
+          [Filters](/docs/reference/javascript/using-filters) and
+          [Modifiers](/docs/reference/javascript/using-modifiers).
 
           <Tabs>
           <TabItem value="schema" label="Schema">
@@ -2019,7 +2019,7 @@ pages:
 
       Filters must be applied after any of `select()`, `update()`, `upsert()`,
       `delete()`, and `rpc()` and before
-      [modifiers](/docs/reference/javascript/next/using-modifiers).
+      [modifiers](/docs/reference/javascript/using-modifiers).
 
       ```ts
       const { data, error } = await supabase