Skip to content

Big plugin dev tutorial #1560

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

Open
10 tasks
Akryum opened this issue Jun 13, 2018 · 4 comments
Open
10 tasks

Big plugin dev tutorial #1560

Akryum opened this issue Jun 13, 2018 · 4 comments
Labels
contribution welcome documentation intend to implement The team has the intention to implement this feature at some point. Contribution is also welcome.

Comments

@Akryum
Copy link
Member

Akryum commented Jun 13, 2018

  • Getting started
  • Generator
  • Prompts
  • Modify the webpack config
  • Add a new cli-service command
  • Augment the task in the UI
  • Create a custom task view (client-addon)
  • Display a configuration screen
  • Create a custom page
  • Localize the plugin
@Akryum Akryum added contribution welcome documentation intend to implement The team has the intention to implement this feature at some point. Contribution is also welcome. labels Jun 13, 2018
@pburdette
Copy link
Contributor

@Akryum video or blog format ?

@km333
Copy link

km333 commented Jul 5, 2018

Can it cover the ‘correct’ way to remove vue-cli-plugins?
We have ‘add’ and ‘invoke’ commands but I can’t see any remove commands anywhere, or in the UI. And the generators don’t seem to have this option either (based on the ones I’ve seen so far).
For now it seems we have to look at old git commits, remove lines from package.json, config files, and plugin .js files. And then npm uninstall from local.

As an aside I think the way some generators actually change and replace core .vue and core config files will not be a sustainable practice even though it seems to be standard now. ‘Pluggable’ means they can be unplugged too right? Food for thought I hope.

@Akryum
Copy link
Member Author

Akryum commented Jul 5, 2018

@km333 This is unrelated to this issue, please open another one.

@elevatebart
Copy link
Contributor

That is an amzing idea, is it something that you would like to do? Something that you wish a Pull Request in the docs for?
Because I would be interrested in both.

I believe you might want to add testing to this list:
How to test your plugin & what to test your plugin for.
The tools of the trade

  • yarn worspaces + lerna
  • cli-test-utils
  • pupettier and execa

Thanks for your answers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution welcome documentation intend to implement The team has the intention to implement this feature at some point. Contribution is also welcome.
Projects
None yet
Development

No branches or pull requests

4 participants