Closed maliakmal closed 2 years ago
Try deleting the node_modules as well as lockfile and reinstall again.
I've tried that infact I do an npm clear cache everytime after deleting node_modules folder and the package lock json file. Its still not working.
Its giving a Parser error in the templates - is this an issue likely with version of Angular used?
Possible. ngx-editor v13. requires angular 13.
I totally forgot about the overrides
option. can you try
{
"overrides": {
"ngx-editor": {
"@types/prosemirror-commands": "1.0.4",
"@types/prosemirror-history": "1.0.3",
"@types/prosemirror-inputrules": "1.0.4",
"@types/prosemirror-keymap": "1.0.4",
"@types/prosemirror-model": "1.16.1",
"@types/prosemirror-schema-list": "1.0.3",
"@types/prosemirror-state": "1.2.8",
"@types/prosemirror-view": "1.23.1",
"prosemirror-commands": "1.2.2",
"prosemirror-history": "1.2.0",
"prosemirror-inputrules": "1.1.3",
"prosemirror-keymap": "1.1.5",
"prosemirror-model": "1.16.1",
"prosemirror-schema-list": "1.1.6",
"prosemirror-state": "1.3.4",
"prosemirror-view": "1.23.12"
}
}
}
See https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides
I totally forgot about the
overrides
option. can you try{ "overrides": { "ngx-editor": { "@types/prosemirror-commands": "1.0.4", "@types/prosemirror-history": "1.0.3", "@types/prosemirror-inputrules": "1.0.4", "@types/prosemirror-keymap": "1.0.4", "@types/prosemirror-model": "1.16.1", "@types/prosemirror-schema-list": "1.0.3", "@types/prosemirror-state": "1.2.8", "@types/prosemirror-view": "1.23.1", "prosemirror-commands": "1.2.2", "prosemirror-history": "1.2.0", "prosemirror-inputrules": "1.1.3", "prosemirror-keymap": "1.1.5", "prosemirror-model": "1.16.1", "prosemirror-schema-list": "1.1.6", "prosemirror-state": "1.3.4", "prosemirror-view": "1.23.12" } } }
See https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides
HI @sibiraj-s After Adding these getting this error, I have deleted node modules, yarn.lock file and then yarn install and built my angular 11 app. ngx-editor version is 8.1.1.
Ah, that means the fix seems to be working. Try to downgrade the versions published with ngx-editor v8. What I sent was from nearly recent versions of the editor,
See https://unpkg.com/browse/ngx-editor@8.1.1/package.json here for the required versions.
And just to verify the fix. if it doesn't work with yarn. can you try with npm once?
@sibiraj-s , Our project has dependency over yarn can't use npm and tried downgrading versions also but it's still showing the same error.
Try these versions.
"overrides": {
"ngx-editor": {
"@types/prosemirror-commands": "1.0.4",
"@types/prosemirror-history": "1.0.2",
"@types/prosemirror-inputrules": "1.0.4",
"@types/prosemirror-keymap": "1.0.4",
"@types/prosemirror-model": "1.12.0",
"@types/prosemirror-schema-list": "1.0.3",
"@types/prosemirror-state": "1.2.6",
"@types/prosemirror-view": "1.17.1",
"prosemirror-commands": "1.1.7",
"prosemirror-history": "1.1.3",
"prosemirror-inputrules": "1.1.3",
"prosemirror-keymap": "1.1.4",
"prosemirror-model": "1.13.3",
"prosemirror-schema-list": "1.1.4",
"prosemirror-state": "1.3.4",
"prosemirror-view": "1.18.1",
"prosemirror-transform": "1.4.0"
}
}
Added prosemirror-transform
new. I tested this in angular 11. ngx-editor v8. Everything works fine. The error you mentioned is gone after this.
Thanks @sibiraj-s it worked!!!
Closing the issue as it has a clear workaround/fix.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in the thread.
What happened?
I'm getting the following error all of a sudden after upgrading Angular and using the new version of ngx-editor. This is the error stack I'm getting>
This is my package.json file
What happened was I'd started facing the same issue as was reported a few days ago on 406 - the issue didn't get sorted but inadvertently now the above error has started to occur - work has stalled and I've tried everything. Any ideas how to finally resolve this?
Version
v13.0.0
Angular Version
v12.0.5
What browsers are you seeing the problem on?
No response
Link to reproduce
No response
Relevant log output
Willing to submit a PR?
No response