Update Ajv version to prevent spurious warnings #412
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates
[email protected]
to[email protected]
.When building via Webpack, there’s some spurious warnings coming from
ajv
-- see ajv-validator/ajv#117.A solution is to just add the following snippet to our
webpack.config.js
to ignore these warnings. This isn’t possible though if a dev is building via the Angular CLI as it actually doesn’t expose the underlying Webpack config.In the referenced issue above, the author addresses the issue was fixed in
[email protected]
(see ajv-validator/ajv#117 (comment)). Since their latest release is currently at5.1.0
though, I've updatedajv
to that.Tests all pass and the project still works great as before! Just no more warnings when building via Webpack or the Angular CLI now! Lemme know if I missed something!