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
Would it be possible to revert this change in a new patch version, deprecate the version that contains this change and finally publish a major version with the new engines in order to respect semver?
Many thanks,
Cristiano.
The text was updated successfully, but these errors were encountered:
Hi, the latest version of
rollup-plugin-esbuild
contains this change: https://github.com/egoist/rollup-plugin-esbuild/pull/356/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519L56, which changes the supported engines in a non-backwards-compatible way. This is a breaking change, and it's currently breaking all projects that use this plugin (or have dependencies that use this plugin) that are incompatible withrollup-plugin-esbuild
's engines range (without doing anything, just a cleannpm install
).Would it be possible to revert this change in a new patch version, deprecate the version that contains this change and finally publish a major version with the new engines in order to respect semver?
Many thanks,
Cristiano.
The text was updated successfully, but these errors were encountered: