composition-api | Composition API plugin for Vue | REST library

You need to define companies in data function:

You do not seem to have the files you build via vue in a folder that is served by GitHub Pages. Go to the repository settings in GitHub and choose "Pages". There you can switch the branch and the folder in the branch that should be served. Currently only "/" (root) or "/docs" are allowed. See the GitHub Pages Docs on this

For your use case, changing this to "/docs" and renaming your "dist" folder to "docs" after building your page / changing the output folder in your compiler should do the trick. Take note that it will take a few minutes for the new index.html to be served instead of the current Readme after changing this.

Just in case it helps someone down the road, it turned out that I was using wrong version of PropType in the component to define my v-model prop. The real PropType class should be imported like this:

One workaround is to convert the v-select's items to strings before binding it. You could use Array.prototype.map with the String constructor as the argument:

I think you can handle the form processing in the save function (and possibly remove the onSubmit function).

The preferable method in modular environment (which Vue 3 setup is commonly is) is to just import api in places where it's used, regardless of whether it's used inside or outside the component.

The solution with Vue global property originated at the time when Vue applications weren't necessarily modular so they relied on Vue instance as global application scope. Currently it's suitable only for properties that are primarily used in a template and require boilerplate code to import and expose them. The example is $t in vue-i18n.

The solution with provide/inject is usable for cases that need dependency injection. A common case is a library that require dependencies to be loosely coupled. Another one is that a dependency depends on component hierarchy and may vary between components.

The solution with window should be avoided, unless application is divided into separate scripts that cannot interact through common JS modules. Even then the problem is that a script that defines global variable should be loaded before those that use it.

In the vue setup function, unlike in data, you don't have access to this, so this.$t is undefined in your rules in the setup function:

I think the problem is, that there is no "re-render" between setting the data and trying to search it in the "ui"(inputs) list. Try to add await nextTick()after your found.items.push. Then vue can re-render and the v-forwill add the item to inputs.

Node version could be a problem. That windows-build-tools is required for the installation indicates there's binary dependency that is potentially incompatible with current Node version. Binary NPM dependencies usually provide a subset of precompiled binaries for a specific package version, where a combination of platform and Node.js version that can be considered safe or supported. For any other combination, binary package needs to be compiled for current platform with build tools. This doesn't always mean that the package is incompatible but this is common.

For example, node-sass (doesn't seem to be used here) has different versions that correspond to specific Node.js versions and provides precompiled binaries for a supported subset; for unsupported Node.js version it falls back to compilation during installation process and most likely fails.

It's unknown which dependency causes this problem in this case, this needs to be reviewed in npm/yarn logs.

In order to avoid this situation, Node version could be matched with old one. Project dependencies need to be freshly installed because node_modules in use has been already tied to currently used Node version.