onDidChangeConfiguration is not a function error in both `wrapper-react` and standard use. #709

brochington · 2024-07-15T22:06:27Z

I'm receiving a very similar error to #686:

contextKeyService.js:82 Uncaught (in promise) TypeError: this._configurationService.onDidChangeConfiguration is not a function
    at new ConfigAwareContextValuesContainer (contextKeyService.js:82:1)
    at new ContextKeyService (contextKeyService.js:314:1)
    at InstantiationService._createInstance (instantiationService.js:120:1)
    at InstantiationService._createServiceInstance (instantiationService.js:224:1)
    at InstantiationService._createServiceInstanceWithOwner (instantiationService.js:212:1)
    at InstantiationService._createAndCacheServiceInstance (instantiationService.js:203:1)
    at InstantiationService._safeCreateAndCacheServiceInstance (instantiationService.js:161:1)
    at InstantiationService._getOrCreateServiceInstance (instantiationService.js:147:1)
    at Object.get (instantiationService.js:70:1)
    at lifecycle.js:38:1
ConfigAwareContextValuesContainer @ contextKeyService.js:82
ContextKeyService @ contextKeyService.js:314
_createInstance @ instantiationService.js:120
_createServiceInstance @ instantiationService.js:224
_createServiceInstanceWithOwner @ instantiationService.js:212
_createAndCacheServiceInstance @ instantiationService.js:203
_safeCreateAndCacheServiceInstance @ instantiationService.js:161
_getOrCreateServiceInstance @ instantiationService.js:147
get @ instantiationService.js:70
(anonymous) @ lifecycle.js:38
invokeFunction @ instantiationService.js:77
startup @ lifecycle.js:36
await in startup (async)
commitLayoutEffectOnFiber @ react-dom.development.js:23344
commitLayoutMountEffects_complete @ react-dom.development.js:24727
commitLayoutEffects_begin @ react-dom.development.js:24712
commitLayoutEffects @ react-dom.development.js:24651
commitRootImpl @ react-dom.development.js:26862
commitRoot @ react-dom.development.js:26721
finishConcurrentRender @ react-dom.development.js:26020
performConcurrentWorkOnRoot @ react-dom.development.js:25848
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533

Same error occurs when using the wrapper-react as well as a more general approach:

const wrapper = new MonacoEditorLanguageClientWrapper();
await wrapper.init(getMonacoWrapperConfig());

Turning off HMR and liveReload results in the same error.

It's possible that this error is related to the bundler I'm using (rsbuild/rspack), but I've been able to get regular Monaco Editor working mostly out of the box.

I've create a test repro repo. Should just be able to npm install, npm run dev to see the error.

The text was updated successfully, but these errors were encountered:

CGNonofr · 2024-07-16T08:31:12Z

@kaisalmen As always, the issue is multiple package version installed

[email protected] uses [email protected] and you're using @codingame/[email protected], instead of the 6.0.3

kaisalmen · 2024-07-16T09:56:02Z

@CGNonofr there must/should occur peerDependeny warnings. I have to check that independently

wangyanci · 2024-08-01T03:41:14Z

similar error

CGNonofr · 2024-08-01T07:47:39Z

Did you check for multiple package version installed?

mxvsh · 2024-09-24T12:27:41Z

i am also getting the same error, i have spent more than 5 hours trying to setup LSP into Monaco editor. Why there isn't any guide, I have tried looking the those examples, they are really confusing.

There are no guide or tutorial or blogs posted recently, all of them are outdated.

mxvsh · 2024-09-24T12:28:22Z

i am using the same versions listed in the example repository -
but still getting the error

contextKeyService.js:81 Uncaught (in promise) TypeError: this._configurationService.onDidChangeConfiguration is not a function

i only changed these packages because there version was updated

		"monaco-editor-wrapper": "next",
		"monaco-languageclient": "next",

mxvsh · 2024-09-24T12:29:38Z

here is my package.json

"@codingame/monaco-vscode-keybindings-service-override": "8.0.4",
"@codingame/monaco-vscode-theme-defaults-default-extension": "8.0.4",
"@codingame/monaco-vscode-typescript-basics-default-extension": "8.0.4",
"@codingame/monaco-vscode-typescript-language-features-default-extension": "8.0.4",
"@monaco-editor/react": "^4.6.0",
"@typefox/monaco-editor-react": "next",
"monaco-editor": "npm:@codingame/monaco-vscode-editor-api@~8.0.4",
"monaco-editor-wrapper": "next",
"monaco-languageclient": "next",
"react": "^18.3.1",
"react-dom": "^18.3.1",
"vscode": "npm:@codingame/monaco-vscode-api@~8.0.4"

CGNonofr · 2024-09-24T13:38:15Z

i am also getting the same error, i have spent more than 5 hours trying to setup LSP into Monaco editor. Why there isn't any guide, I have tried looking the those examples, they are really confusing.

There are no guide or tutorial or blogs posted recently, all of them are outdated.

Feel free to make one as soon as you manage to make it work ;)

What is the result of npm list vscode?

mxvsh · 2024-09-24T14:19:39Z

i am also getting the same error, i have spent more than 5 hours trying to setup LSP into Monaco editor. Why there isn't any guide, I have tried looking the those examples, they are really confusing.
There are no guide or tutorial or blogs posted recently, all of them are outdated.

Feel free to make one as soon as you manage to make it work ;)

What is the result of npm list vscode?

sure, i will make a blog on it once i manage to set it up!! 😃

here is the log file btw of your command-

vscode.log

CGNonofr · 2024-09-24T15:10:44Z

You have both vscode@npm:@codingame/[email protected] and vscode@npm:@codingame/[email protected], because of [email protected]

mxvsh · 2024-09-24T15:29:34Z

@CGNonofr so what do i do? 😄

mxvsh · 2024-09-24T15:32:40Z

@CGNonofr if you have a working code/repository with you, could you please share it with me 😄

CGNonofr · 2024-09-24T15:34:17Z

There is a compatibility table

Also you probably shouldn't use the next version since there is a more recent stable version

mxvsh · 2024-09-24T15:35:30Z

okay, i am trying to make a new project add one by one from that table, and i will let you know

kaisalmen · 2024-09-24T15:38:01Z

@mxvsh basically do not mix different versions of the same dependency in one project. Have you successfully checked out this repo, build everything and used the examples? The README is quite detailed. Which information is missing / unclear. Enhancement PRs are appreciated.

mxvsh · 2024-09-24T15:41:32Z

from the table, i believe monaco-editor-react is @monaco-editor/react because monaco-editor-react on npm is outdated (last updated 6 years ago). But when I try to install @monaco-editor/react, I get this error.

This error happened while installing a direct dependency of /Users/monawwar/dev/poc/monaco-editor

The latest release of @monaco-editor/react is "4.6.0".
Other releases are:
  * beta: 4.5.0-beta.0

CGNonofr · 2024-09-24T15:42:20Z

You're confusing @monaco-editor/react with monaco-editor-react which are 2 different libraries

CGNonofr · 2024-09-24T15:44:02Z

I think it's @typefox/monaco-editor-react you're looking for, and you've already installed it along with the other one

CGNonofr · 2024-09-24T15:44:53Z

btw @kaisalmen why is one namespaced and not the other?

kaisalmen · 2024-09-24T15:46:52Z

@CGNonofr monaco-editor-react was there ages ago and not developed by us. I namespaced @typefox/monaco-editor-react because of that.

kaisalmen · 2024-09-24T15:47:32Z

I should have done the same with monaco-editor-wrapper

mxvsh · 2024-09-24T15:50:02Z

@CGNonofr i tried in a completely new project - but still getting that error.

i checked with the table, it all matches with one row.

here is the repository-

https://github.com/mxvsh/monaco-editor-poc

mxvsh · 2024-09-24T15:52:10Z

here is the log btw npm list vscode

vscode.log

CGNonofr · 2024-09-24T15:52:14Z

A simple check to the pnpm-lock.yaml shows that you have both 8.0.4 and 9.0.3 versions of monaco-vscode-api

mxvsh · 2024-09-24T15:52:52Z

@CGNonofr but i just created a new project - how come it installed two different versions?

i am sorry - but can you tell me how to fix it 😢

CGNonofr · 2024-09-24T15:54:00Z

by installing a dependency A directly, and having another dependency B that requires the dependency A with another version

CGNonofr · 2024-09-24T15:55:37Z

As the compatibility table states, [email protected] should not be used with v9 of monaco-vscode-api (and all other @CodinGame packages)

also, you don't need monaco-editor

mxvsh · 2024-09-24T15:56:40Z

when i run without installing monaco-editor package, i get this error

CGNonofr · 2024-09-24T15:56:55Z

btw @kaisalmen, having monaco-editor in the compatibility table is quite confusing, it's only for informative purpose and we should probably say that it shouldn't be installed

mxvsh · 2024-09-24T15:57:16Z

"dependencies": {
  "@codingame/monaco-vscode-keybindings-service-override": "^9.0.3",
  "@codingame/monaco-vscode-theme-defaults-default-extension": "^9.0.3",
  "@codingame/monaco-vscode-typescript-basics-default-extension": "^9.0.3",
  "@codingame/monaco-vscode-typescript-language-features-default-extension": "^9.0.3",
  "@typefox/monaco-editor-react": "^4.5.3",
  "monaco-editor-wrapper": "5.5.3",
  "react": "^18.3.1",
  "react-dom": "^18.3.1"
},

CGNonofr · 2024-09-24T15:58:31Z

monaco editor should be installed as an alias to @codingame/monaco-editor-api instead

Which should be the case because it's declared in the dependencies of monaco-editor-wrapper

kaisalmen · 2024-09-24T16:00:51Z

@mxvsh use 8.0.4 instead of 9.0.3 for all monaco-vscode dependencies. 9.x is not yet supported.

"@codingame/monaco-vscode-keybindings-service-override": "^9.0.3",

mxvsh · 2024-09-24T16:04:13Z

Thanks! That error is gone with the following dependency -

"dependencies": {
  "@codingame/monaco-vscode-keybindings-service-override": "8.0.4",
  "@codingame/monaco-vscode-theme-defaults-default-extension": "8.0.4",
  "@codingame/monaco-vscode-typescript-basics-default-extension": "8.0.4",
  "@codingame/monaco-vscode-typescript-language-features-default-extension": "8.0.4",
  "@typefox/monaco-editor-react": "^4.5.3",
  "monaco-editor": "npm:@codingame/[email protected]",
  "monaco-editor-wrapper": "5.5.3",
  "react": "^18.3.1",
  "react-dom": "^18.3.1"
},

but I got another error - 😭

Uncaught (in promise) Error: Unable to figure out browser width and height
    at getClientArea (dom.js:315:13)
    at LayoutService.layout (layout.js:352:40)
    at new LayoutService (layout.js:63:14)
    at _InstantiationService._createInstance (instantiationService.js:120:24)
    at instantiationService.js:238:38

kaisalmen · 2024-09-24T16:35:01Z

@mxvsh please share a repo with your example than we can have a look.

mxvsh · 2024-09-24T16:42:20Z

@kaisalmen i shared before, i will share it again 😃

https://github.com/mxvsh/monaco-editor-poc

kaisalmen · 2024-09-24T16:53:44Z

Sorry, I missed that.

caner-cetin · 2024-10-13T00:05:19Z

There is a compatibility table

Also you probably shouldn't use the next version since there is a more recent stable version

holy fucking shit both projects needs an AIO package desperately. I have wrote example Python code 1:1, WS connection is alive, all is fine on server, and I get the same error

Uncaught (in promise) TypeError: this._configurationService.onDidChangeConfiguration is not a function

problem is package json is taller than the berlin wall right now, I know there is a version that works (mxvsh s versions doesnt work for me), but looking at compat table and reinstalling all of these is really, really unintiutievevj (forgot the word).

Thanks for this awesome project by the way. It is perfect for everything, and it is perfect when used like a level between monaco, like instead of connecting the lower level Monaco to the LSP and sending all commands by myself, I can just use monaco languageserver library. but I want the whole package like in Python example, and, holy hell, this is worrying me.

edit: mxvsh s versions does not work with either bun, npm, pnpm, everything I throw at this thing refuses to work with same error

#686 (comment)

last edit because it is 4 am in the morning, here is my latest dependency tree. I feel like no need for MRP, you can reproduce it in same way with the mxvsh's MRP.

i dont know what is wrong, but I have spent 6 hours on this error. tried almsot all compatible versions.

kaisalmen · 2024-10-21T07:59:54Z

@mxvsh and @caner-cetin I was busy with other things and then away last week. I will provide feedback this week.

Harry-Drew-CyanBytes · 2024-11-12T20:37:00Z

I'm getting the same issue.

I'm specifically getting the issue when trying to integrate with React. When I download the example project it works fine: https://github.com/TypeFox/monaco-languageclient but when i try to produce a minimal recreation of just the react part (with a language server) i get the error. Any news or updates on this issue and does anyone have a barebones example of a react implementation (not in a massive mono repo) 😄

caner-cetin · 2024-11-12T20:42:07Z

I cant provide help or support, moved onto Ace Editor instead of Monaco and I cant remember what I did. best I can say is check versions of packages, at least package.json and vite config file in main example folder is helpful.

kaisalmen · 2024-12-09T07:39:45Z

Package mismatch seems to be a repeating problem. I have opened #789 to track this and hopefully find a more reliable solution for it.

onDidChangeConfiguration is not a function error in both wrapper-react and standard use. #709

onDidChangeConfiguration is not a function error in both wrapper-react and standard use. #709

Comments

brochington commented Jul 15, 2024

CGNonofr commented Jul 16, 2024 • edited Loading

kaisalmen commented Jul 16, 2024 • edited Loading

wangyanci commented Aug 1, 2024

CGNonofr commented Aug 1, 2024

mxvsh commented Sep 24, 2024

mxvsh commented Sep 24, 2024 • edited Loading

mxvsh commented Sep 24, 2024

CGNonofr commented Sep 24, 2024

mxvsh commented Sep 24, 2024 • edited Loading

CGNonofr commented Sep 24, 2024 • edited Loading

mxvsh commented Sep 24, 2024

mxvsh commented Sep 24, 2024

CGNonofr commented Sep 24, 2024

mxvsh commented Sep 24, 2024

kaisalmen commented Sep 24, 2024 • edited Loading

mxvsh commented Sep 24, 2024 • edited Loading

CGNonofr commented Sep 24, 2024

CGNonofr commented Sep 24, 2024

CGNonofr commented Sep 24, 2024

kaisalmen commented Sep 24, 2024 • edited Loading

kaisalmen commented Sep 24, 2024

mxvsh commented Sep 24, 2024

mxvsh commented Sep 24, 2024 • edited Loading

CGNonofr commented Sep 24, 2024

mxvsh commented Sep 24, 2024 • edited Loading

CGNonofr commented Sep 24, 2024

CGNonofr commented Sep 24, 2024 • edited Loading

mxvsh commented Sep 24, 2024

CGNonofr commented Sep 24, 2024

mxvsh commented Sep 24, 2024

CGNonofr commented Sep 24, 2024

kaisalmen commented Sep 24, 2024

mxvsh commented Sep 24, 2024 • edited Loading

kaisalmen commented Sep 24, 2024

mxvsh commented Sep 24, 2024

kaisalmen commented Sep 24, 2024

caner-cetin commented Oct 13, 2024 • edited Loading

kaisalmen commented Oct 21, 2024

Harry-Drew-CyanBytes commented Nov 12, 2024

caner-cetin commented Nov 12, 2024

kaisalmen commented Dec 9, 2024

onDidChangeConfiguration is not a function error in both `wrapper-react` and standard use. #709

onDidChangeConfiguration is not a function error in both `wrapper-react` and standard use. #709

CGNonofr commented Jul 16, 2024 •

edited

Loading

kaisalmen commented Jul 16, 2024 •

edited

Loading

mxvsh commented Sep 24, 2024 •

edited

Loading

mxvsh commented Sep 24, 2024 •

edited

Loading

CGNonofr commented Sep 24, 2024 •

edited

Loading

kaisalmen commented Sep 24, 2024 •

edited

Loading

mxvsh commented Sep 24, 2024 •

edited

Loading

kaisalmen commented Sep 24, 2024 •

edited

Loading

mxvsh commented Sep 24, 2024 •

edited

Loading

mxvsh commented Sep 24, 2024 •

edited

Loading

CGNonofr commented Sep 24, 2024 •

edited

Loading

mxvsh commented Sep 24, 2024 •

edited

Loading

caner-cetin commented Oct 13, 2024 •

edited

Loading