Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardize dependency logic #1992

Closed
RunDevelopment opened this issue Jul 21, 2019 · 1 comment · Fixed by #1998
Closed

Standardize dependency logic #1992

RunDevelopment opened this issue Jul 21, 2019 · 1 comment · Fixed by #1998

Comments

@RunDevelopment
Copy link
Member

Motivation
We have how many different implementations for loading and handling dependencies?
The following components all have their own distict logic:

Description
Standardize the dependency logic.

It should be able to handle both languages and plugins so that we can use it at the download page. This also includes reloading and support for required CSS files.

It would also be nice if it could deal with aliases, but that's optional.

Info
I already implemented something similar here so that should be a good starting point.

@mAAdhaTTah
Copy link
Member

Yeaaaaah, I had to write an implementation for the babel plugin too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants