Slava

Following your notation it would be: ```js // Input Code import 'foo'; import { Foo } from 'foo'; import Foo from 'foo'; // Output ↓ ↓ ↓ ↓ ↓ ↓...

@jaywcjlove wow, that was quick, thank you. I will try it out.

I've tried to use the following configuration: ```js { loader: "babel-loader", options: { plugins: [ [ "babel-plugin-transform-remove-imports", { test: /^core-js\//, remove: 'effects', }, ], ], }, } ``` to remove...

@jaywcjlove actually, looking at your implementation I can see a small misunderstanding. I was hoping that `remove: 'effects'` would work with `test` option, so both criteria should be met in...

If you don't mind I would propose the following API: ```javascript { loader: "babel-loader", options: { plugins: [ [ "babel-plugin-transform-remove-imports", { cases: [ // multiple cases could be specified {...

@jaywcjlove I believe that when `removeAll` option is used, the usage of `cases` should throw error to signify that those two options are mutually exclusive.

Hello @trentm, could you look into this, please?

The weirdest thing is that the `latest` dist tag on npm points to the `5.0.0-beta.2` version (which is not even in the "releases" section on GitHub), while it should point...

Hello! Thank you for your hard work, ajv is a very cool project. Please pardon my interruption. > JavaScript support for 2^53 is usually sufficient... Usually yes, however, I'm working...

I see, @ryanmcgrath , you should add a deprecation notice to the README and use https://docs.npmjs.com/cli/deprecate to notify the users during module installation then, I think. Maybe even add a...