Remove lodash.deepClone in favor of Object.assign

[gm112]

Removes a dependency in favor of a native equivalent!

[Pridestalkerr]

Object.assign() creates a shallow copy as opposed to lodash.cloneDeep().
They would only be equivalent if all keys inside those objects are primitives, otherwise everything else (such as nested objects) will have the same reference.

This change may actually work, but really need to make sure that mutations arent performed on the cloned objects.

[mcampa]

seems reasonable, thanks

[lawandothman]

Hey @mcampa

I don't think this has been removed properly from the build output cuz I've started getting this error in 2.1.1

Error: :esbuild: ✘ [ERROR] Could not resolve "lodash.clonedeep"
. build:esbuild:     ../../node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected][email protected]/node_modules/trpc-to-openapi/dist/esm/generator/paths.mjs:2:22:
. build:esbuild:       2 │ import cloneDeep from 'lodash.clonedeep';
. build:esbuild:         ╵                       ~~~~~~~~~~~~~~~~~~
. build:esbuild:   You can mark the path "lodash.clonedeep" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle.

I can still see references to it in dist/esm/adapters/node-http/core.mjs on npm too for example

[mcampa]

Ahh, thanks for letting me know @lawandothman. I probably published to npm without running a build first. I need to setup a Github Action that publishes the build to npm to prevent this from happening in the future.

I just published 2.1.2 to fix the issue, you can use that version. Please let me know if you find any other issue.

[lawandothman]

Yep that fixed the build @mcampa - thank you 🙂