The reason why we need to remove browserify is to avoid encouraging developers to try using browserify when developing a plugin due to the fact that you cannot just chain the use of tsify as a plugin and then use babelify. It won't work. You'll need to create a separate task to transpile XJS Framework with ES6 as a target, then transpile your plugin including XJS to es5.
Webpack on the other hand would simply make use of ts-loader and babel-loader, which would work out of the box without any additional headaches.
The reason why we need to remove browserify is to avoid encouraging developers to try using browserify when developing a plugin due to the fact that you cannot just chain the use of tsify as a plugin and then use babelify. It won't work. You'll need to create a separate task to transpile XJS Framework with ES6 as a target, then transpile your plugin including XJS to es5.
Webpack on the other hand would simply make use of ts-loader and babel-loader, which would work out of the box without any additional headaches.