ajv-validator
Please document if/how standalone validation code generation can be run by Webpack
What version of Ajv you are you using? 8.8.2
What problem do you want to solve? Get rid of 'unsafe-eval' in our CSP by using standalone validation code.
What do you think is the correct solution to problem? Let Webpack generate the standalone validation code on build.
Will you be able to implement it? Sadly no.
Hi, i too am facing the same issue. Did you happen to find any solutions for this?
Most likely, it would be easier to run compilation using ajv-cli as part of the build and then import compiled files from their target locations as you would do with your own code - I don’t think there will be anything special here with WebPack, compiled schema is a normal JavaScript code.
Depending on the schema, compiled files may have dependency on ajv runtime folder, but as long as ajv is available and can be resolved (via require) during the build it shouldn’t be a problem.
For example you can check out table package that uses build time schema compilation.
i have created standalone code for my schema but my validation schema is quite large and hence i'm facing build issues. so i'm looking into how i can optimise that. as of now i have compiled and generated a standalone schema file. then bundled it using esbuild and imported it directly into the app. But this is increasing the app build time
The approach is correct, and the build time will be slightly increased indeed - I don’t think much can be done about it, it’s what it is. Why do you need optimising it? It’s still should be under 1 min build time for most applications, am I right?
after adding standalone schema the app:javascript size increased from 2.02 mb to 4.35mb. build times are close to 3 minutes and out of memory heap issues are also popping up.
The approach is correct, and the build time will be slightly increased indeed - I don’t think much can be done about it, it’s what it is. Why do you need optimising it? It’s still should be under 1 min build time for most applications, am I right?
is there any provision to resolve ajv-formats or other similar require statements?
cause export statements are throwing these errors
