How to access the new instance of vue in the secondary wrapper file of axios, and why the instance of vuex accessed is undefined

vuex:

import axios from "axios";
import ip, {token} from "./ip";
import store from "@/store";
console.log(store); // storeundefined

import Store from "@/utils/store";


// cookie
axios.defaults.withCredentials = false;
// 
axios
  .interceptors
  .request
  .use(config => {
    config.headers.common["Authorization"] = Store.get("token");
    return config;
  }, error => {
    return Promise.reject(error);
  });

export default axios;

Node.js vuex vue-router vue.js javascript

Mar.18,2021

was not introduced to the directory folder that should be released;
store in src/store/index.js?

    import Vue from 'vue'
    import Vuex from 'vuex'
    
    const state={ ...}
    ...
    
    Vue.use(Vuex)
    
    const store = new Vuex.Store({
      state,
      getters,
      actions,
      mutations
    })
    
    export default store

import store from '@/store'
xxx = store.getters.token

const store = require ('.. / store/index');
console.log (store); / / Store {_ committing: false, _ actions: { .

but you can import

using the require method.

has it been solved? I also encountered this problem.
my store/index:

import Vue from 'vue'
import Vuex from 'vuex'
import app from './modules/app'
import user from './modules/user'
import getters from './getters'

Vue.use(Vuex)

const store = new Vuex.Store({
  modules: {
    app,
    user
  },
  getters
})

export default store

notice that there is a import user from'. / modules/user'
above and modules/user.js says this:

import { login, logout, getInfo } from '@/api/login'

the following interface is quoted here. Remove this sentence and then be fine. It's strange, but it's definitely illogical.
have you solved it

Previous: The crontab command was not executed on time.

Next: When using the css attribute filter: blur (), why setting z-index does not solve: the after pseudo-element obscures the main element?