Update documentation to the latest version 馃殌 #32
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.
Version 4.0.0-beta16 of documentation just got published.
The version 4.0.0-beta16 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of documentation.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Commits
The new version differs by 11 commits .
73ba79b
Changelog and package for beta16
ab16a20
fix(bin): Remove dead code in documentation.js command (#627)
11fef7d
docs(install): reiterate installation directions in getting started
89fb67f
feat(build): load passed in config option (#625)
363a108
fix(extractors): Document export default value (#623)
381ef48
docs(readme): Add new usage examples to README
5c3b6ba
docs(cli): Improve selection of examples that the CLI tool lists
846ab94
fix(parser): Avoid error about deoptimization on very large files (#621)
8b04029
feat(output): Display type information for typedefs in Markdown and HTML
f9ddb9c
Output typedef content in Markdown and HTML. Fixes #359 (#619)
6998a05
chore(dependencies): Update dependency ranges for all that can be seamlessly upgraded (#617)
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 馃尨