fix(*): fix deps and build process

[adamdehaven]

Summary

Vue Composition API

When utilizing the @vue/composition-api inside of a Kongponent package, the @vue/composition-api needs to be added as a peerDependency to the component package rather than a dependency.

Currently, installing with yarn with the peer flag yarn add {package-name} --peer is broken

You will need to manually add the peerDependencies entry inside the individual component's package.json. For example, inside ./packages/KTable/package.json this is what was added

{
  "peerDependencies": {
    "@vue/composition-api": "^1.2.4"
  }
}

The parent application must then manually add @vue/composition-api to it's package.json as a dependency if utilizing any of the components depending on the package (this is now outlined in the docs for each corresponding component, currently KTable and KCardCatalog).

This is required as the component must use the same instance of the plugin as the parent application, meaning that the plugin has to be added to the parent application's dependencies. This is further outlined in an issue on the composition api repo.

Once Vue 2.7 is released, @vue/composition-api will be directly shipped with it, so this extra step will no longer be needed.

The quote above, taken from the issue, means that we should plan to upgrade Kongponents (and any parent Kong-owned applications, such as khcp, kong-admin, etc.) to 2.7 when released, which will make utilizing the library easier on the user.

Build Process

Update the build process to copy necessary config files in a separate step, leaving them in place until yarn build:cli finishes, then remove from the individual /package/* directories, as other steps in the build process will fail if postcss.config.js files are not left in place (e.g. in KIcon package) until the completion of all package builds.

Docs

Update docs for KTable and KCardCatalog for usage with Composition API.

PR Checklist

• Does not introduce dependencies
• Functional: all changes do not break existing APIs and if so, bump major version.
• Tests pass: check the output of yarn test packages/
• Naming: the files and the method and prop variables use the same naming conventions as other Kongponents
• Framework style: abides by the essential rules in Vue's style guide
• Cleanliness: does not have formatting issues, unused code (e.g., console.logs), or leftover comments
• Docs: includes a technically accurate README, uses JSDOC where appropriate

[netlify]

✔️ Deploy Preview for kongponents ready!

🔨 Explore the source changes: 789ad95

🔍 Inspect the deploy log: https://app.netlify.com/sites/kongponents/deploys/619be08486215f00070f9d4b

😎 Browse the preview: https://deploy-preview-434--kongponents.netlify.app

[kaiarrowood]

This is great!! Thanks Adam!!