Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Upgrade from 7.0.0 to 7.5.x/8.x on Angular 18 will not compile #1122

Open
1 task done
Austinb opened this issue Jan 20, 2025 · 4 comments
Open
1 task done

[BUG] Upgrade from 7.0.0 to 7.5.x/8.x on Angular 18 will not compile #1122

Austinb opened this issue Jan 20, 2025 · 4 comments
Assignees
Labels

Comments

@Austinb
Copy link

Austinb commented Jan 20, 2025

Environment

Please provide as many details as you can:

  • Hosting type
    • [] Form.io
    • Local deployment
      • Version: 7.5.x or 8.x
  • Formio.js version: N/A
  • Frontend framework: Angular 18.2.x using @angular-builders/custom-esbuild
  • Browser: N/A
  • Browser version: N/A
  • Typescript 5.5.4

Steps to Reproduce

This is an upgrade from Angular 17 to Angular 18.2 and upgrading formio/angular from 7.0.0 to 7.5.x or 8.x

Expected behavior

Expect app to compile and run using ng serve {app}

Observed behavior

Application will not compile for ng serve {app}. Throws errors referencing @formio/deprecated-types which is not mentioned in the installation instructions but is fixable. Main issue is the cascade of other errors which appear to be missing dependencies being thrown from pretty much every .ts file within the node_modules/@formio install directory. Unsure if the formio/angular library is expecting other dependencies or what. Rolling back to 7.x with overrides compiles as expected and the usage works as expected within the compiled app.

Also, it does not seem to matter what version of formio/js is installed or bootstrap which is also used.

Example

Running ng serve {app} results in the following errors plus many more being displayed in the console

✘ [ERROR] TS2307: Cannot find module 'types' or its corresponding type declarations. [plugin angular-compiler]

    node_modules/@formio/core/lib/error/FieldError.d.ts:1:34:
      1 │ import { ValidationContext } from 'types';
        ╵                                   ~~~~~~~


✘ [ERROR] TS2307: Cannot find module 'types' or its corresponding type declarations. [plugin angular-compiler]

    node_modules/@formio/core/lib/error/ProcessorError.d.ts:1:33:
      1 │ import { ProcessorContext } from 'types';
        ╵                                  ~~~~~~~


✘ [ERROR] TS2307: Cannot find module 'utils' or its corresponding type declarations. [plugin angular-compiler]

    node_modules/@formio/core/lib/modules/jsonlogic/index.d.ts:1:48:
      1 │ import { BaseEvaluator, EvaluatorOptions } from 'utils';
        ╵                                                 ~~~~~~~


✘ [ERROR] TS2307: Cannot find module 'types' or its corresponding type declarations. [plugin angular-compiler]

    node_modules/@formio/core/lib/process/calculation/index.d.ts:1:98:
      1 │ ...CalculationScope, CalculationContext, ProcessorInfo } from 'types';
        ╵                                                               ~~~~~~~


✘ [ERROR] TS2307: Cannot find module 'types' or its corresponding type declarations. [plugin angular-compiler]

    node_modules/@formio/core/lib/process/clearHidden.d.ts:1:81:
      1 │ ...e, ProcessorContext, ProcessorInfo, ProcessorFnSync } from 'types';
        ╵                                                               ~~~~~~~

@Austinb Austinb added the bug label Jan 20, 2025
@FrozeenHub
Copy link

I've had the same issue with Angular 18.2 and version 8.x

@FrozeenHub
Copy link

This user has gotten the same error:
formio/formio.js#5993

@mail4taz
Copy link

Hi. We're running into the same issue as originally posted. I would be nice if this gets resolved since starting a new project on Angular 17 is no longer an option given LTS end date for it.

@FrozeenHub
Copy link

Hello, i suggest you to check out formio/formio.js#5715 (comment) as it should be fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants