Plugin generator translations and external deps

[lizozom]

Follow up for #55281

The following features should be re-introduced into the new plugin generator

• Plugins should have an optional translations file Allow custom paths in plugin generator #57766
• 3rd party plugins (i.e. in /plugins directory) should have a package.json and support adding external deps.
  Prior to Update plugin generator to generate NP plugins #55281, quite a lot of things were defined in the package.json, making the genration. What should be the minimal deps in that package.json file? @joshdover
• Support generating x-pack plugins (generally specifying a folder) @alexwizp Allow custom paths in plugin generator #57766

[elasticmachine]

Pinging @elastic/kibana-app-arch (Team:AppArch)

[tylersmalley]

I would also like to add that with #55281 we removed the ability for 3rd party plugins to be able to build themselves. This previously was part of the package.json build script which used the plugin-helpers.

[sszilvasi]

Is it currently possible to add external dependencies to 3^rd party NP plugins?

[spalger]

Is it currently possible to add external dependencies to 3rd party NP plugins?

Yes, you can install as many packages from npm as you like. They should be included in the 3rd party plugin's downloaded archive because Kibana doesn't install them when your plugin is installed (to support offline install)

[sszilvasi]

@lizozom @spalger Thanks, the original answer solved my problem.

Just run the following commands in the plugin folder:

npm init
npm install <somepackage>