Data returned from load while rendering is not serializable: Cannot stringify arbitrary non-POJOs

[Bishwas-py]

[FORMS-ACTIONS] Returning something inside fail is giving me the upper error;

return fail(500, {
    message: 'Something went wrong.',
    message_type: 'error',
    alias: 'internal_server_error'
});

but while returning

{
message: 'Something went wrong.',
message_type: 'error',
alias: 'internal_server_error'
}

it works.

It used to work, maybe upgrading on Svelte 5 made something weird here?

Here's what I've been trying to do,

export const via_route_name = (proxy_paths, opt_ = {}) => {
    const action = {
        ['login']: async (event) => {
            // return {
            //                 message: 'Something went wrong.',
            //                 message_type: 'error',
            //                 alias: 'internal_server_error'
            //             }; this works
            return fail(500, {
                message: 'Something went wrong.',
                message_type: 'error',
                alias: 'internal_server_error'
            }); // this doesn't
        }
    }
    return {
        ...action
    }
};

in +page.server.ts

export const actions = via_route_name(['login'], {allow_cookies: true})

via_route_name is a proxy, and it return actions. There are conditions attached to via_route_name function, but I have reduced it to simplify the issue.

[Bishwas-py]

The jist I am getting is, the imported via_route_name has a different object id for ActionFailure. SvelteKit's base is probably comparing ActionFailure objects; as the ActionFailure by fail(... returned via via_route_name (assuming ActionFailure_(via_route_name) is different to the kit's codebase ActionFailure (assuming ActionFailure_(kit_codebase);

object ActionFailure_(via_route_name)  is not the instance of `ActionFailure_(kit_codebase)`

Hence, svelte thought it's a foreign object, and did not continue on serializing the status and the data attributes.

[Bishwas-py]

Basically, I was working for a library, @friendofsvelte/django-kit, using npm link for another project, so there was probably an object recognition issue. So, I just published a dev version of the lib to npm, and installed it. It's working for now. I so wish that if it worked on npm link, it would have been awesome.