The version 4.0.0 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 anchor-js.
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.
Release Notes4.0.0
Breaking Changes:
Any Links or generated IDs containing a < or > character will have them removed. Those characters are not appropriate in IDs because they are part of the CSS language spec. See #81.
We removed h1 from the default selector applied when anchors.add() is called without arguments. Before: h1, h2, h3, h4, h5, h6. After: h2, h3, h4, h5, h6. See #75.
Features:
Added the ability to link to other IDs on the page (like those on wrapper or <section> elements). This means you can use AnchorJS for highlighted sections. See the docs, or the related issues: #83 and #87
Many documentation improvements and clarifications.
Bug Fixes:
Prevents a console error that would occur when running add() on a selector with no elements, followed by a chained method. See #79
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 4.0.0 of anchor-js just got published.
The version 4.0.0 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 anchor-js. 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.
Release Notes
4.0.0Breaking Changes:
<or>character will have them removed. Those characters are not appropriate in IDs because they are part of the CSS language spec. See #81.h1from the default selector applied whenanchors.add()is called without arguments. Before:h1, h2, h3, h4, h5, h6. After:h2, h3, h4, h5, h6. See #75.Features:
<section>elements). This means you can use AnchorJS for highlighted sections. See the docs, or the related issues: #83 and #87Bug Fixes:
add()on a selector with no elements, followed by a chained method. See #79Commits
The new version differs by 22 commits.
bf22c0fRelease 4.0.0! :tada:f6b930a:arrow_up: update dev-dependenciesef2ef26:memo: adds documentation for unclear concepts and new features39dfc92:bug: prevents an error when chaining to an add() having no elements475e2e7:wrench: fix broken gh-pages builds by removing symlinks3a77c5aremove all experiements except for the symlink one4106584:microscope: experiement with symlinks and github pagesb8760b1:truck: move docs from gh-pages into the \docs folder0677604:memo: docs: fix the broken image in the README0da16faAdd a visual check of the section highlighting feature.85469bbMerge PR #83 (section highlighting feature)a9661f9rename new attribute to minimise conflictsd307263fix header in readme9ed2ab0support IDs specified with data attributee902ff2:arrow_up: update dev-dependenciesThere are 22 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: