docs: fix: "devalue is a lot faster but insecure to use on the server" #6092
Labels
✅ accepted-PRs-welcome
Feature proposal is accepted and ready to work on
📚 documentation / examples
Improvements or additions to documentation
Area of Improvement
Why is the following section in the docs correct:
that section is located here: https://trpc.io/docs/server/data-transformers
devalue can be insecure if you are using
uneval
andeval
but you can also usestringify
andparse
in thedevalue
library to avoid the usage ofeval
.I find a transformer example which is just using
devalue
to be much friendlier than that weird mix ofsuperjson
anddevalue
togetherLink to related docs
https://trpc.io/docs/server/data-transformers
Additional information
No response
👨👧👦 Contributing
Funding
The text was updated successfully, but these errors were encountered: