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
Thanks for submitting the ticket (ticket assigned). Also - we're going to keep rollup 1.x support, for now, since some users might actually be using that version range.
…s to allow an matching version of '@rollup/pluginutils' to be installed alongside 'rollup' v3.
- Removed '@types/rollup', and '@types/sass', from dev-deps due to these not being used in development, since they're just 'stub' packages (their implementation packages export/contain their own typings), and are deprecated, they are safe to removed.
- scripts - Updated 'clean-and-run-downlevel-dts' script, to ignore 'directory not found' warning, when attempting to delete the './ts*' directory, before genating it's new content, since removing the directory, before content generation, is what we're trying to do there.
- gh-actions - Removed unrequired 'github packages' action - We're only publishing to 'npm' for now.
When installing or updating dependencies with Pnpm, it nags with the following error since I updated to Rollup 3.17.2.
I bet that this plugin will not work with Rollup v1 anymore, and it seems to work with the latest Rollup versions.
Maybe change the Rollup version range on package.json to something like
^2 || ^3
? Or then something more specific – there is a npm semantic version calculator by Npm.The text was updated successfully, but these errors were encountered: