question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

callback.apply is not a function

See original GitHub issue

Describe the bug

vite.config.js

import { fileURLToPath, URL } from 'node:url'

import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'

import Components from 'unplugin-vue-components/vite'
import { AntDesignVueResolver } from 'unplugin-vue-components/resolvers'

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [
    vue(),
    Components({
      resolvers: [AntDesignVueResolver()],
    })
  ],
  resolve: {
    alias: {
      '@': fileURLToPath(new URL('./src', import.meta.url))
    }
  }
})

image

Reproduction

https://github.com/limengning/unplugin-vue-components-bug.git

System Info

System:                                                    
    OS: Windows 10 10.0.19045                                
    CPU: (4) x64 Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz     
    Memory: 6.18 GB / 15.89 GB                               
  Binaries:                                                  
    Node: 18.12.0 - C:\Program Files\nodejs\node.EXE         
    npm: 8.19.2 - C:\Program Files\nodejs\npm.CMD            
  Browsers:                                                  
    Edge: Spartan (44.19041.1266.0), Chromium (107.0.1418.26)
    Internet Explorer: 11.0.19041.1566

Used Package Manager

npm

Validations

  • Follow our Code of Conduct
  • Read the Contributing Guide.
  • Check that there isn’t already an issue that reports the same bug to avoid creating a duplicate.
  • Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
  • The provided reproduction is a minimal reproducible of the bug.

Issue Analytics

  • State:open
  • Created a year ago
  • Reactions:6
  • Comments:10

github_iconTop GitHub Comments

9reactions
ajslatercommented, Oct 31, 2022

Can confirm that this bug does not exist if you revert to v0.22.8

5reactions
codingcncommented, Nov 1, 2022

v0.22.8 is ok

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to solve "TypeError: callback.apply is not a function"?
apply is not a function . Simply because { upsert: true } is not a function. Share.
Read more >
Callback.apply is not a function - The freeCodeCamp Forum
It means that there was a type error. Something in JS has “thrown” an error. It is saying, “When I evaluate 'callback.apply', what...
Read more >
TypeError: callback is not a function in JavaScript | bobbyhadz
The "callback is not a function" error occurs when we define a callback parameter to a function, but invoke the function without passing...
Read more >
TypeError: callback.apply is not a function · Issue #293 - GitHub
I am using multiple-concurrency (with value 10) but it's not working for me . Test runs for few pages and then everything stops...
Read more >
How to solve “TypeError: callback.apply is not a function”
Javascript – How to solve “TypeError: callback.apply is not a function” ... I am doing a university project and I've read every post...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found