getcurrentInstance has been removed from the official api area because the project is now being upgraded from vue2 to vue3. Some public global properties and methods are bound in main.js. How to migrate this? If the properties and instances of the component cannot be obtained if

[lessin123]

getcurrentInstance has been removed from the official api area because the project is now being upgraded from vue2 to vue3. Some public global properties and methods are bound in main.js. How to migrate this? If the properties and instances of the component cannot be obtained if

[lessin123]

The current API only provides app.config.globalProperties to set global properties and methods, but does not provide corresponding properties and methods to obtain the set global values. This is a bit puzzling.

[LinusBorg]

I can't decipher what your problem is. Can you share an example of the problem you are trying to solve ?

[lessin123]

The first picture declares two global methods filter and goTop in main.js. The second picture declares and obtains global methods in the component. This is a very common way, but I didn't find it in the api document. The documentation for getCurrentInstance is available. I'm worried that this approach will not be acceptable in the future, but I haven't found any other official solution provided.

[LinusBorg]

I see. You are migrating to script setup?

global properties are kind of a relic of the options API and as such only usable through that. in script setup, we always recommend to use provide / inject for more explicit code and better TS / IDE support.

// main.js
app.provide('gotTo', () => ....)

<script setup>
import { inject } from 'vue'
const goTo = inject('goTo')
</script>

As a sidenote for this example: I would not use a global property nor a provide for this kind of very general utility method - I would just import it from a utils folder:

import { goTo } from '../utils/goto.js'

provides usually make more sense when working with code that works with component-specific interactions (i.e. parent/child interactions), or library integrations

[lessin123]

In fact, if you use the defineComponents method, because the project is vue2, it is not intended to be replaced all at once, otherwise the risk is a bit high. Also, app.config.globalProperties cannot be used, right? You can only use provide/inject. ?

[LinusBorg]

globalProperties is meant to be used with Options API. You can see an example in the docs: https://vuejs.org/api/application.html#app-config-globalproperties

So for the examples you provided, you can access them like this in Options API:

export default defineComponent({
  mounted() {
    this.goTop
  }
})

if you have components used script setup or use the setup() function in a normal script, you would need to use provide/inject (as shown in my example above).

If you have both kinds of components mixed in your codebase (i.e. because you are migrating to script setup), you can also use both globalProperties and provide:

// main.js
const goTop = () => ....
// for `<script setup>` / `setup()` components
app.provide('gotTop', goTop)
// for "old-school" Options API components
app.config.globalProperties.goTop = goTop

Once you have fully migrated away from Options API components, you can just delete the globalProperties definitions

[jh-leong]

ref: stackoverflow Vue 3: Is getCurrentInstance() deprecated?

getCurrentInstance() was originally documented in 4-Oct-2020, but that was later removed in 31-Aug-2021 in a major refactoring of the Composition API docs by the creator of Vue (Evan You). Despite its removal from the docs, getCurrentInstance() still:

• is widely used in Vue core.
• is not documented as deprecated in code.
• is exported as part of the Advanced API.

Given that it's an undocumented internal API, use it with caution.

[lessin123]

Yes, this is said to be abandoned. In fact, many projects are using this method. Secondly, the official did not provide a solution. It only provided the statement of app.config.globalProperties but did not say how to obtain it.

[Pentadome]

One annoyance of vue is that advanced apis are rarely documented

[lessin123]

The project is currently being restructured and upgraded to vue3. The project size is very large, with more than 1 million rows. I am worried about the instability of the API in the future. I discovered this problem during the early research.