You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In neutrinojs/neutrino#184 we were trying to work out why we couldn't use the language customisation feature from 49ea502, even though we thought we were using the latest version of this plugin (6.0.1).
It turns out that the most recent (in terms of date) release of this plugin was given the version 5.6.0, which is a lower number than the two releases prior to it (which were 6.0.0 and 6.0.1). This means people using ^6.0.1 as a version range are not actually getting the most recent version of the plugin. (See the NPM versions/dates below)
Please could a new release be published with version 6.0.2 or higher, so the recent fixes are picked up?
Counter-intuitively the most recent version of the package is actually
5.6.0, rather than 6.0.0 or 6.0.1 due to a publishing error. See:
jaketrent/html-webpack-template#59
Hi!
In neutrinojs/neutrino#184 we were trying to work out why we couldn't use the language customisation feature from 49ea502, even though we thought we were using the latest version of this plugin (6.0.1).
It turns out that the most recent (in terms of date) release of this plugin was given the version 5.6.0, which is a lower number than the two releases prior to it (which were 6.0.0 and 6.0.1). This means people using
^6.0.1
as a version range are not actually getting the most recent version of the plugin. (See the NPM versions/dates below)Please could a new release be published with version 6.0.2 or higher, so the recent fixes are picked up?
The text was updated successfully, but these errors were encountered: