Front ui после добавление Frontend component ошибка

Вопросы и проблемы
#1

Здравствуйте, После добавление Frontend component (entity management) ошибка
Gradle Daemon started in 1 s 479 ms

Task :bil-core:assembleDbScripts UP-TO-DATE
Task :bil-core:dbScriptsArchive UP-TO-DATE
Task :bil-core:beansXml UP-TO-DATE
Task :bil-global:beansXml UP-TO-DATE
Task :bil-global:processResources UP-TO-DATE
Task :bil-global:buildInfo UP-TO-DATE
Task :bil-global:compileJava UP-TO-DATE
Task :bil-global:classes UP-TO-DATE
Task :bil-global:jar UP-TO-DATE
Task :bil-core:compileJava NO-SOURCE
Task :bil-core:processResources UP-TO-DATE
Task :bil-core:classes UP-TO-DATE
Task :bil-core:jar UP-TO-DATE
Task :bil-core:sourceJar UP-TO-DATE
Task :bil-core:assemble UP-TO-DATE
Task :bil-core:cleanConf UP-TO-DATE
Task :bil-core:deploy
Task :bil-front:nodeSetup UP-TO-DATE
Task :bil-front:npmSetup SKIPPED
Task :bil-front:npmInstall UP-TO-DATE

Task :bil-front:buildFrontend

bilim@0.1.0 build D:\Java\bilim\modules\front
react-scripts build

Creating an optimized production build…
Failed to compile.

.\src\routing.ts
Cannot find module: ‘./app/newentity/NewEntityCards’. Make sure this package is installed.

You can install this package by running: npm install ./app/newentity/NewEntityCards.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! bilim@0.1.0 build: react-scripts build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bilim@0.1.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\user\AppData\Roaming\npm-cache_logs\2020-06-26T12_49_22_842Z-debug.log

Task :bil-front:buildFrontend FAILED

FAILURE: Build failed with an exception.

  • What went wrong:
    Execution failed for task ‘:bil-front:buildFrontend’.

Process ‘command ‘D:\Java\bilim\modules\front.gradle\nodejs\node-v10.14.1-win-x64\npm.cmd’’ finished with non-zero exit value 1

  • Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

  • Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
Use ‘–warning-mode all’ to show the individual deprecation warnings.
See https://docs.gradle.org/5.6.4/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 22s
16 actionable tasks: 2 executed, 14 up-to-date
6:49:23 PM: Task execution finished ‘deploy’.

#2

Здравствуйте,

Скорее всего экран создается для новой сущности, которой еще нет в модели фронтенда (TypeSript SDK), необходимо обновить модель. Мы знаем об этом неудобстве и будем работать над тем чтобы сделать синхронизацию модели автоматической.

#3

после выполнение команды npm run update-model все равно ошибка

There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.

The react-scripts package provided by Create React App requires a dependency:

“babel-eslint”: “10.0.1”

Don’t try to install it manually: your package manager does it automatically.
However, a different version of babel-eslint was detected higher up in the tree:

D:\Java\Repository\untitled1\node_modules\babel-eslint (version: 10.0.3)

Manually installing incompatible versions is known to cause hard-to-debug issues.

If you would prefer to ignore this check, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That will permanently disable this message but you might encounter other issues.

To fix the dependency tree, try following the steps below in the exact order:

  1. Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
  2. Delete node_modules in your project folder.
  3. Remove “babel-eslint” from dependencies and/or devDependencies in the package.json file in your project folder.
  4. Run npm install or yarn, depending on the package manager you use.

In most cases, this should be enough to fix the problem.
If this has not helped, there are a few other things you can try:

  1. If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
    This may help because npm has known issues with package hoisting which may get resolved in future versions.

  2. Check if D:\Java\Repository\untitled1\node_modules\babel-eslint is outside your project directory.
    For example, you might have accidentally installed something in your home folder.

  3. Try running npm ls babel-eslint in your project folder.
    This will tell you which other package (apart from the expected react-scripts) installed babel-eslint.

If nothing else helps, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That would permanently disable this preflight check in case you want to proceed anyway.

P.S. We know this message is long but please read the steps above :slight_smile: We hope you find them helpful!

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! untitled1@0.1.0 build: react-scripts build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the untitled1@0.1.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\user\AppData\Roaming\npm-cache_logs\2020-06-29T18_41_46_850Z-debug.log

Task :app-front:buildFrontend FAILED

FAILURE: Build failed with an exception.

  • What went wrong:
    Execution failed for task ‘:app-front:buildFrontend’.

Process ‘command ‘D:\Java\Repository\untitled1\modules\front.gradle\nodejs\node-v10.14.1-win-x64\npm.cmd’’ finished with non-zero exit value 1

  • Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

  • Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
Use ‘–warning-mode all’ to show the individual deprecation warnings.
See https://docs.gradle.org/5.6.4/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 5s
16 actionable tasks: 2 executed, 14 up-to-date
12:41:46 AM: Task execution finished ‘deploy’.