Framework: Use imports for WordPress modules instead of the wp global

[youknowriad]

part of #1205

I would appreciate a quick review for this to avoid many conflicts :)

[ellatrix]

Love it. Do you think we can remove the wp global from eslint too, for better testing?

[ellatrix]

If we need it anywhere else for external stuff, we can force window.wp.

[youknowriad]

@iseulde Not against it, but maybe there're too much wp usage left for this. (All the wp.api, wp.media usages)

[ellatrix]

Hm, ran it and it passes?

[ellatrix]

Aha forgot it inherits from other config. Will remove commit

[ellatrix]

In that case, can we change that with Webpack? It seems strange to still have both after this PR.

[ellatrix]

Mostly asking because I'm not sure how we'll prevent it from being introduced again unknowingly.

[youknowriad]

In that case, can we change that with Webpack?

I'm trying but failing to define these modules in webpack. It seems to accept wp as an external module but not wp.media. Any idea?

[ellatrix]

Oh, this has been attempted before: #742.

[ellatrix]

Yeah, wp.media itself is a function... :)

[youknowriad]

Yeah, I'm thinking we'd need to add a namespace to resolve this import { media } from '@wordpress';

Anyway, I'm keen to merge this as a first step and see how to solve the external wp modules issue.

[aduth]

Capitalization: We should probably prefer TinyMCE, createTinyMCEElement