Prerequisites
🚀 Feature Proposal
Use the AJV code option to decide if the standalone code generator would emit CJS (require/module) or ESM (import/export) instead of hardcoding require and module.exports as shown below in the standalone.js file
|
const { dependencies } = require('fast-json-stringify/lib/standalone') |
|
|
|
const { Serializer, Validator } = dependencies |
|
|
|
const serializerState = ${JSON.stringify(serializer.getState())} |
|
const serializer = Serializer.restoreFromState(serializerState) |
|
|
|
${ajvDependencyCode} |
|
|
|
module.exports = ${contextFunc.toString()}(validator, serializer)` |
Motivation
Typescript and ESM users will have to go through some build system configurations to resolve the require in ESM runtime headache during development. Especially that the StandaloneValidator from the @fastify/ajv-compiler package respects the ESM AJV option out of the box.
If we can leverage the serializerOptions, Fastify users in ESM envirmenment can easily use a standalone serializers with the AJV options
ajv: {
code: { source: true, esm: true }
}
Example
No response
Prerequisites
🚀 Feature Proposal
Use the AJV
codeoption to decide if the standalone code generator would emit CJS (require/module) or ESM (import/export) instead of hardcodingrequireandmodule.exportsas shown below in thestandalone.jsfilefast-json-stringify/lib/standalone.js
Lines 14 to 23 in 74c35c0
Motivation
Typescript and ESM users will have to go through some build system configurations to resolve the
requirein ESM runtime headache during development. Especially that theStandaloneValidatorfrom the@fastify/ajv-compilerpackage respects the ESM AJV option out of the box.If we can leverage the serializerOptions, Fastify users in ESM envirmenment can easily use a standalone serializers with the AJV options
Example
No response