Error build when update wijmo to 5.20241.19

Posted by: diego.pacanhella on 18 December 2024, 4:27 pm EST

    • Post Options:
    • Link

    Posted 18 December 2024, 4:27 pm EST

    hello, I’m updating wijmo 5.20211.781 to version 5.20241.19. I updated the license and also the style to “.scss”, but when I run a build, a typing error occurs. In the previous version, the build was normal. Could you help me?

    I’m using Angular 11

    typescript ~4.2.1

    Error:

    [error] RangeError: Maximum call stack size exceeded
        at parseNonArrayType (C:\dev\workspace\frontend\TaxProf_aafm-br-onvio-accounting-cost-components\node_modules\typescript\lib\typescript.js:30003:28)
        at parsePostfixTypeOrHigher (C:\dev\workspace\frontend\TaxProf_aafm-br-onvio-accounting-cost-components\node_modules\typescript\lib\typescript.js:30098:24)
        at parseTypeOperatorOrHigher (C:\dev\workspace\frontend\TaxProf_aafm-br-onvio-accounting-cost-components\node_modules\typescript\lib\typescript.js:30157:20)
        at parseUnionOrIntersectionType (C:\dev\workspace\frontend\TaxProf_aafm-br-onvio-accounting-cost-components\node_modules\typescript\lib\typescript.js:30186:20)
        at parseIntersectionTypeOrHigher (C:\dev\workspace\frontend\TaxProf_aafm-br-onvio-accounting-cost-components\node_modules\typescript\lib\typescript.js:30197:20)
        at parseUnionOrIntersectionType (C:\dev\workspace\frontend\TaxProf_aafm-br-onvio-accounting-cost-components\node_modules\typescript\lib\typescript.js:30186:20)
        at parseUnionTypeOrHigher (C:\dev\workspace\frontend\TaxProf_aafm-br-onvio-accounting-cost-components\node_modules\typescript\lib\typescript.js:30200:20)
        at parseTypeWorker (C:\dev\workspace\frontend\TaxProf_aafm-br-onvio-accounting-cost-components\node_modules\typescript\lib\typescript.js:30291:24)
        at doOutsideOfContext (C:\dev\workspace\frontend\TaxProf_aafm-br-onvio-accounting-cost-components\node_modules\typescript\lib\typescript.js:28153:30)
        at parseType (C:\dev\workspace\frontend\TaxProf_aafm-br-onvio-accounting-cost-components\node_modules\typescript\lib\typescript.js:30284:20)

  • Posted 19 December 2024, 2:33 am EST

    Hi Diego,

    The error message you have mentioned has no reference to Wijmo packages in the call stack which is why it would be difficult to pin point the exact cause of it.

    Please note Angular 11 Compiler only supports TypeScript >=4.0.0 and <4.2.0.

    Also, Wijmo no longer provides support for Angular versions earlier than 14, starting from Wijmo build 5.20231.890-rc. This change is due to Angular requiring TypeScript 4.8 and up. While Wijmo itself can function with TypeScript 3.2, Wijmo’s Angular modules must now require TypeScript 4.8 to support the latest Angular releases.

    If you still wish to use our latest Wijmo build with Angular 11, you can do so by utilizing our legacy packages instead of the Angular2 packages. To access these legacy packages, please add ‘@grapecity/wijmo.angular2legacy.all’ to your package.json file. You can refer to the attached sample for it’s implementation, we have used the legacy packages in the sample.

    As for the issue, I tried to reproduce this issue with Angular 11, TypeScript Version 4.1.6 and @mescius/wijmo.angular2legacy.all v5.20241.19, 5.20242.21 and 5.20242.30 and I wasn’t able to reproduce this issue. Please share a sample application reproducing this issue or edit the attached sample application such that it reproduces the issue and send it back to us so we can test this issue at our end and get back to you accordingly.

    wijmo-angular11-app.zip

  • Posted 26 December 2024, 12:11 pm EST

    I followed the project you sent me as a basis. I fixed the imports to use legacy. But when you try to run it, it says that there is no dependency on grapecity but it no longer exists

    An unhandled exception occurred: The target entry-point “@onviobr/accounting-costs” has missing dependencies:

    • @grapecity/wijmo
  • Posted 27 December 2024, 8:04 am EST

    Hi Diego,

    Please try removing the ‘package.lock.json’ file and all the packages in the node_modules folder and then try re-installing the packages, if not already tried. Also, try deleting the cache files from your project, if any.

    Please make sure you have updated the legacy package names in the ‘package.json’ file and in all the component and module files where they are imported.

    If the issue still persist, please share a small sample in which the issue can be replicated, as we are not able to replicate the issue on our end. We need a sample so that we can investigate the issue further and assist you accordingly.

    Regards

  • Posted 22 January 2025, 9:06 am EST

    Do you have support from Brazil?

  • Posted 23 January 2025, 9:21 am EST

    Hi Diego,

    Yes, we provide global support, including for customers in Brazil. You can reach us using the following contact details:

    Phone: 1.800.858.2739 | 412.681.4343

    You can also post any queries on our forums portal, where our team and community members will be happy to assist you. For private case discussions, we have a dedicated portal available at the following link:

    https://developer.mescius.com/my-account/my-support

    Regards

  • Posted 24 January 2025, 10:26 am EST

    Should grapecity’s license be the same as mescius legacy?

  • Posted 30 January 2025, 2:38 am EST

    Hi Diego,

    Yes, GrapeCity’s license is the same as the Mescius legacy license. If you face any issues, please let us know, and we’ll be happy to assist you.

    Regards

  • Posted 31 January 2025, 3:42 pm EST

    I managed to make it work. I updated Angular to 13 and Typescript to 4.6

    apparently solved it and without needing the version of mescius legacy

  • Posted 3 February 2025, 2:17 am EST

    Hi Diego,

    Thank you for the information, we are glad that the issue is resolved now.

    Regards

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels