Closed elementalTIMING closed 9 months ago
Hi, does the error appear on the web console? Do you only get this one line?
If the module is an SCSS file perhaps there is a wrong import statement that only triggers on production.
If not there must be any production settings that leads to this error. Try checking the production options and/or tsconfig options.
Hi, does the error appear on the web console? Do you only get this one line?
If the module is an SCSS file perhaps there is a wrong import statement that only triggers on production.
If not there must be any production settings that leads to this error. Try checking the production options and/or tsconfig options.
Well, this is the full stack trace I can see in the console. Indeed it's a SCSS project. What makes me a bit nervous is that it was working before like a charm but with any prev update this error appeared suddenly.
Error: couldn't load module ace/theme/idle_fingers or it didn't call define
at R (https://sscm-dev.speedskatingnews.info/6583.b941ada31ba19ef5.js:1:828762)
at https://sscm-dev.speedskatingnews.info/6583.b941ada31ba19ef5.js:1:461664
at Array.forEach ()
at A (https://sscm-dev.speedskatingnews.info/6583.b941ada31ba19ef5.js:1:461641)
at https://sscm-dev.speedskatingnews.info/6583.b941ada31ba19ef5.js:1:462770
at Q (https://sscm-dev.speedskatingnews.info/6583.b941ada31ba19ef5.js:1:441236)
at https://sscm-dev.speedskatingnews.info/6583.b941ada31ba19ef5.js:1:440539
at https://sscm-dev.speedskatingnews.info/6583.b941ada31ba19ef5.js:1:462752
at p (https://sscm-dev.speedskatingnews.info/6583.b941ada31ba19ef5.js:1:461754)
at l.onload.l.onreadystatechange (https://sscm-dev.speedskatingnews.info/6583.b941ada31ba19ef5.js:1:451784)
Did you try this? https://stackoverflow.com/questions/71909337/aceeditoruncaught-error-couldnt-load-module-ace-theme
Btw I recommend to always censor production domains before posting.
Did you try this? https://stackoverflow.com/questions/71909337/aceeditoruncaught-error-couldnt-load-module-ace-theme
This sounds like a baseHref issue. Open network tab and check for files that couldn't be found. Perhaps it's a redirection issue.
It becomes even more strange. It has nothing to do with jodit or ngx-jodit. It comes from another component that shouldn't been loaded at this point but for what reason ever Angular decided to do it.
But thank you so much for your support!
Did you try the steps from my previous comment? Stackoverflow and the network tab thing?
Did you try the steps from my previous comment? Stackoverflow and the network tab thing?
I tried, but without success. Maybe I've placed it at the wrong place. I have to check this a bit more in detail.
Closing this issue. Hope you found a solution
Hi,
I know that this topic is a bit off-topic and has probably nothing to do with the ngx-jodit itself. But I hope that you have an idea of a solution. Since using the ngx-jodit and the jodit latest beta versions I get the following error message:
I'm using a real standard configuration and (which is the most curious) - this error comes only on my production system. From that point of view it's a bit hard to debug. Do you already have seen this issue?