Obviously, we're not going to change our application architecture and maintain an additional project
I think I was not clear enough in my message. I just meant you don't really need to rebuild all your packages to angular-10 to use them with your Angular-10 application. Same for bryntum packages. It's still compatible since it's built with any version from angular 7 to angular 10 according to Angular documentations.
Anyway, we were able to update it for you.
I used your _shared.zip
and my example together and checked all once again on 2 different machines.
It's working stable in both machines. The only thing I saw again and need to aware you about, it's an error I reported before that I saw in your app too: https://github.com/angular/angular/issues/38436
It's Angular bug which is not fixed yet (possibly happens only for version 10), but we found a workaround: if you have this error after you launch prod version (the result of npm run build
command), just call npm run build
once again without removing anything. After the second build the error will be fixed. That's strange, but this is how it works. It's definitely a bug with angular build optimization process, same I think about the problem you reported.
The next steps that we could do: check the zip attached. You will find 2 folders inside: advanced-10
and _shared
. Unzip them into your angular
directory as you did before.
Goto _shared
and run npm i
inside (check package.json
to make sure it uses angular 10).
Goto advanced-10
and run npm i
(check package.json
to make sure it uses angular 10) and after that npm run build
to build prod version.
After that try to open the prod version of the app (it will be in dist/angular-8
subfolder).
If you see "selectors of null" error - this is that I told you about, check the info above - it may be easily fixed.
All works like a charm. Please, try to reproduce your problem once again. If you will see that, please zip all that you can and send to us, with steps to reproduce and all details about your environment, version of bryntum scheduler, your browser, your OS. We really need to find the cause.
All best,
Alex