can we still post json to an endpoint?

[rossi-jeff]

I've been looking through both the docs and this forum and can't seem to find the right file structure or syntax to make an enpoint that can have json posted to it with fetch, create a record with prisma, and the return the new record. You know, like an api.

I've been a fan of svelte for a while but I'm a little lost with the new stuff.

[geoffrich]

If you don't want to use form actions, you can still create a +server.js file with a POST method that can accept JSON.

import { json } from '@sveltejs/kit';
import type { RequestHandler } from './$types';
 
export const POST = (async ({ request }) => {
  const { a, b } = await request.json();
  return json(a + b);
}) satisfies RequestHandler;

Docs

[rossi-jeff]

I was basically doing this in +server.ts

export const POST: RequestHandler = async ({ request }) => {}

and getting a 500 with no indication that the function was being executed

[geoffrich]

If you don't return anything from the request handler, you will get a 500 back and see an error message in the dev server console:

Error: Invalid response from route /api: handler should return a Response object
    at render_endpoint@/node_modules/ (sveltejs/kit/src/runtime/server/endpoint.js:52:10)
    at <anonymous> (<anonymous>)

If you are returning something and still getting an error, then please provide a reproduction to help troubleshoot.

[rossi-jeff]

still no joy

src/routes/api/codebreaker/+server.ts

import { db } from '$lib/db';
import type { ArgsCodeBreakerCreate } from '../../../types/args-code-breaker-create';
import { GameStatus } from '../../../types/game-status.enum';
import { getColorEnumValue } from '$lib/get-color-enum-value';
import type { RequestHandler } from './$types';
import { error } from '@sveltejs/kit';

export const POST: RequestHandler = async ({ request }) => {
	const data: ArgsCodeBreakerCreate = await request.json();
	if (!data) throw error(400, 'bad request');
	console.log(data);
	const { Colors, Columns } = data;
	const now = new Date();
	const codeBreaker = await db.client().codeBreaker.create({
		data: {
			Columns: Columns ?? 0,
			Colors: Colors?.length ?? 0,
			Status: GameStatus.Playing,
			CreatedAt: now,
			UpdatedAt: now
		}
	});
	if (Colors && Colors.length) {
		for (const color of Colors) {
			await db.client().codeBreakerCode.create({
				data: {
					CodeBreakerId: codeBreaker.Id,
					Color: getColorEnumValue(color),
					CreatedAt: now,
					UpdatedAt: now
				}
			});
		}
	}
	return new Response(JSON.stringify(codeBreaker));
};

src/routes/codebreaker/+page.svelte

const createGame = async (event: any) => {
		const Colors: string[] = event.detail.Colors;
		const Columns: number = event.detail.Columns;
		try {
			const response = await fetch('/api/codebreaker', {
				method: 'POST',
				headers: {
					'Content-Type': 'application/json'
				},
				body: JSON.stringify({ Colors, Columns })
			});
			if (response.ok) game = await response.json();
			console.log(response);
		} catch (error) {
			console.log(String(error));
		}
	};

response

Response {type: 'basic', url: 'http://localhost:5173/api/codebreaker', redirected: false, status: 500, ok: false, …}
body
: 
(...)
bodyUsed
: 
false
headers
: 
Headers {}
ok
: 
false
redirected
: 
false
status
: 
500
statusText
: 
"Internal Server Error"
type
: 
"basic"
url
: 
"http://localhost:5173/api/codebreaker"
[[Prototype]]
: 
Response

[eltigerchino]

sveltekit offers a helper function for returning the response json(...)

This replaces new Response(JSON.stringify(...))

[rossi-jeff]

this was in console running dev

ReferenceError: exports is not defined
    at /src/games-db/index-browser.js:2:23
    at instantiateModule (file:///mnt/c/Users/rossi/git/games-full-stack-svelte/node_modules/vite/dist/node/chunks/dep-5e7f419b.js:52224:15)

[rossi-jeff]

this may be a prisma error

[rossi-jeff]

after going down a rabbit hole this is indeed an issue with prisma and a commonjs export

[rossi-jeff]

after installing @originjs/vite-plugin-commonjs I'm now at

TypeError: __vite_ssr_import_0__.PrismaClient is not a constructor

time to look at other ORMs