-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
Let plugins add information to the Readme.md #3547
Comments
Running hook after the |
Any update on this? I wrote a carefully crafted README in my template months ago and only today discovered that it is completely ignored! Or at least overwritten later. I tried manually writing to it using I have a super hacky workaround but I don't like it: setTimeout(() => {
// Update README.md.
}, 10000); |
So the current situation is this: There is a utility function for generating the readme file. It requires the final version of the In order for it to pickup on all the scripts defined by the official plugins (e.g. eslint, jest, etc) it is only called after all the generators have been called. To make the readme editable by other plugins, the creation process would have to be split.
As a further improvement, the script descriptions should be added directly by the generators of the official plugins. This way any preset and other plugins can override all of the readme content. |
Now I'm using this method to solve it. Writing the following code at API api.onCreateComplete(() => {
process.env.VUE_CLI_SKIP_WRITE = true
}) Because the function |
What problem does this feature solve?
Plugins and presets often need to add long-lasting generic information into a project, for example, a preset would add in deployment or configuration details to be done by developers outside of the Vue CLI.
What does the proposed API look like?
api.extendReadme(MarkDownFormattedString)
The readme would then generate a section based on the plugin/preset that inserted the string so that it can be included in the generated readme.md
The text was updated successfully, but these errors were encountered: