f:null 1a:T46c,Hey @BenZ just saw you upvoted. Incase it's of use to you, apologies realised I hadn't updated my thread. A sort of non-perfect solution i created was a utility function that wraps the return statement in any query, it is based off of the supported superjson types, i havent had any issues with it so far, your mileage may vary though! ```typescript /* eslint-disable @typescript-eslint/no-explicit-any */ import { ObjectId } from "bson"; import { Url } from "url"; // SuperJSON supported types type SuperJSONSupportedTypes = | Date | Set | Map | RegExp | undefined | null | bigint | Url type Jsonify = T extends ObjectId ? string : T extends SuperJSONSupportedTypes ? T : T extends object ? { [K in keyof T]: Jsonify } : T; export const jsonify = (data: T): Jsonify => { return data as unknown as Jsonify; }; ``` e.g ```typescript get_all_users: authenticatedProcedure.query(async ({ ctx }) => { const users = await User.find({}) .select<{ user_name: string; }>("user_name") .lean(); return jsonify(users); }), ```1b:T46c,Hey @BenZ just saw you upvoted. Incase it's of use to you, apologies realised I hadn't updated my thread. A sort of non-perfect solution i created was a utility function that wraps the return statement in any query, it is based off of the supported superjson types, i havent had any issues with it so far, your mileage may vary though! ```typescript /* eslint-disable @typescript-eslint/no-explicit-any */ import { ObjectId } from "bson"; import { Url } from "url"; // SuperJSON supported types type SuperJSONSupportedTypes = | Date | Set | Map | RegExp | undefined | null | bigint | Url type Jsonify = T extends ObjectId ? string : T extends SuperJSONSupportedTypes ? T : T extends object ? { [K in keyof T]: Jsonify } : T; export const jsonify = (data: T): Jsonify => { return data as unknown as Jsonify; }; ``` e.g ```typescript get_all_users: authenticatedProcedure.query(async ({ ctx }) => { const users = await User.find({}) .select<{ user_name: string; }>("user_name") .lean(); return jsonify(users); }), ```1c:T46c,Hey @BenZ just saw you upvoted. Incase it's of use to you, apologies realised I hadn't updated my thread. A sort of non-perfect solution i created was a utility function that wraps the return statement in any query, it is based off of the supported superjson types, i havent had any issues with it so far, your mileage may vary though! ```typescript /* eslint-disable @typescript-eslint/no-explicit-any */ import { ObjectId } from "bson"; import { Url } from "url"; // SuperJSON supported types type SuperJSONSupportedTypes = | Date | Set | Map | RegExp | undefined | null | bigint | Url type Jsonify = T extends ObjectId ? string : T extends SuperJSONSupportedTypes ? T : T extends object ? { [K in keyof T]: Jsonify } : T; export const jsonify = (data: T): Jsonify => { return data as unknown as Jsonify; }; ``` e.g ```typescript get_all_users: authenticatedProcedure.query(async ({ ctx }) => { const users = await User.find({}) .select<{ user_name: string; }>("user_name") .lean(); return jsonify(users); }), ```13:[["$","title","0",{"children":"How to treat mongoose/mongodb ObjectIDs as their serialized string values on the frontend? - tRPC"}],["$","meta","1",{"name":"description","content":"$1a"}],["$","meta","2",{"name":"robots","content":"index, follow"}],["$","link","3",{"rel":"canonical","href":"https://discord-questions.trpc.io/m/1263123263727468565"}],["$","meta","4",{"property":"og:title","content":"How to treat mongoose/mongodb ObjectIDs as their serialized string values on the frontend? - tRPC"}],["$","meta","5",{"property":"og:description","content":"$1b"}],["$","meta","6",{"property":"og:site_name","content":"tRPC"}],["$","meta","7",{"property":"og:image",