Машинописный текст: node_modules/имена классов/индекс.d.ts:13:13 Псевдоним типа «Аргумент» по кругу ссылается на себя

#typescript #maven #npm #aem

Вопрос:

Любая информация об этой ошибке, которую я получаю при создании своего проекта. В Интернете не так много информации о том, как устранить эту проблему. Я запускаю typescript 4.2.4

У меня также нет этих имен классов/index.d.ts ни в одном каталоге. Поэтому я также не могу ничего исправить в файле.

Будет ли это экземпляр неправильной установленной версии или исправлена какая-то логика?

 
[48:02.5]  type checking finished in 12.00 s

[ ERROR ]  TypeScript: node_modules/classnames/index.d.ts:13:13
           Type alias 'Argument' circularly references itself.

     L12:  export type Mapping = { [key: string]: any };
     L13:  export type Argument = Value | Mapping | Argument[];

[48:02.5]  build failed in 12.14 s

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! jll-ipl@0.0.1 stencil:build: `stencil build --docs`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the jll-ipl@0.0.1 stencil: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!     /Users/eduardo.gc/.npm/_logs/2021-05-18T15_48_02_641Z-debug.log
Rendering Complete, saving .css file...
Wrote CSS to /Users/eduardo.gc/Desktop/git/property-listings/ui.apps/src/main/content/jcr_root/etc/designs/global-property-listings/ipl.css
Wrote Source Map to /Users/eduardo.gc/Desktop/git/property-listings/ui.apps/src/main/content/jcr_root/etc/designs/global-property-listings/ipl.css.map
ERROR: "stencil:build" exited with 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! jll-ipl@0.0.1 build:js: `npm-run-all stencil:build`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the jll-ipl@0.0.1 build:js 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!     /Users/eduardo.gc/.npm/_logs/2021-05-18T15_48_03_571Z-debug.log
ERROR: "build:js" exited with 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! jll-ipl@0.0.1 build: `npm-run-all -p build:*`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the jll-ipl@0.0.1 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!     /Users/eduardo.gc/.npm/_logs/2021-05-18T15_48_03_678Z-debug.log
[ERROR] Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
    at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:404)
    at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)
    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:804)
    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:751)
    at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:313)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
 

Ответ №1:

похоже, он изменен в главной ветви, но не выпущен.

https://github.com/JedWatson/classnames/blob/master/index.d.ts

С моей стороны, это нормально, когда я использую 3.8.3. https://devblogs.microsoft.com/typescript/announcing-typescript-3-7-rc/#more-recursive-type-aliases

дважды подтвердите локальную версию машинописного текста.