Call for plugin maintainers: update @theforeman/vendor to version 3

This is a call for plugin maintainers who uses webpack to upgrade their npm module @theforeman/vendor to version ^3.0.0.

We are planning to update foreman core to use v3 of the vendor this Wednesday (2019-11-19T22:00:00Z), notice it has the potential to break your plugin so please respond on time and make sure to upgrade your plugins.

Some useful links:

Feel free to reach out if you need help with the upgrade process.

Thanks!

The last effort migrating to vendor v3 blocked because we found out we need to do packaging for too many babel-<something> modules while we already have a solution for grouping them in one package to simplify the packaging process.

Therefore we created the @theforeman/babel module that contains all the babel modules and groups them together.

We will merge those changes 2019-11-24T22:00:00Z, please update your plugins.

How to upgrade your plugin:

  1. Upgrade your plugin vendor from v1 to v3.
  2. Install @theforeman/babel in your plugin.
  3. Go over your plugin devDependencies and remove all the dependencies that exists in @theforeman/babel package.json file except @theforeman/vendor-dev, do not remove it.
  4. If you are using jest for testing, upgrade jest and babel-jest to v24 (v23 require babel v6)

Thanks

1 Like

Today we merged #7178 so core uses @theforeman/vendor^3.3.2, please update your plugins accordingly.

PRs I created for plugins:

The last migration guide was not valid, to migrate please:

  1. Upgrade your plugin vendor from v1 to v3.
  2. Install @theforeman/builder in your plugin.
  3. Install @theforeman/env in your plugin.
  4. Go over your plugin devDependencies and remove all the dependencies that exists in @theforeman/builder package.json file and in @theforeman/env package.json file

Let me know if you need any help with the migration,

Thanks!

1 Like