The extension depended on old types which are about to be removed. As the code additionally was pretty crufty and didn't provide much in the way of functionality, removing the extension seems to be the best way forward.

I tested it, and it indeed works, but I don't want to depend on a to-be-removed feature.

Using ~ is deprecated and can be removed from your code (we recommend it)

Development has been suspended on this project because QtWebKit was deprecated in favor of QtWebEngine, which is not a suitable replacement for our purposes.

netstat (net-tools) is deprecated, perhaps you want to use other tools (ss, lsof, fuser etc.)

Consider using this rule in place of no-untyped-public-signature which has been deprecated.

Lumberjack 1.0 had a concept of a unit of work id that could be used to tie log messages together. This has been replaced by tags. There is still an implementation of Lumberjack.unit_of_work, but it is just a wrapper on the tag implementation.

now that I realize how easy it is to just manually include this in my app: <%= javascript_include_tag 'xray', nonce: true if Rails.env.development? %> I regret even wasting my time getting it to automatically look for and add a nonce to the auto-injected xray.js script

Wasted too much time getting it to work with old Rubies/Rails, when I think the correct path should be to just remove support for them going forward

This version makes the new client that was added in version 2.6+ the default client, and removes the legacy client. All previously deprecated functionality has been removed (since version 2.5, see below).

Sprockets 3 was a compatibility release to bridge Sprockets 4, and many deprecated things have been removed in version 4.

First, the frame and frameset elements are not deprecated in HTML5, they're obsolete (i.e., they've been removed entirely).

@Deprecated("Use syntax instead.") bool indented

deprecated – plese see / use caly

In brief, @import is being replaced with more explicit @use and @forward rules. Over the next few years Sass @import will be deprecated, and then removed.

It is only soft-deprecated, which means that your code will not break at the moment and no deprecation warning will be displayed, but this constant will be removed in the future.

Additionally, if we ever want to standardize more of JSX we need to start moving away from some of the more esoteric legacy behaviors of React.

E4X is a deprecated specification with deep reaching semantic meaning.

using EventTarget.addEventListener(), and this generally replaces using the old HTML event handler attributes.

webpack ./entry.js bundle.js --module-bind 'css=style!css'