`npm start`抱怨“缺少脚本：启动”，没有运行节点(`npm start` complains “missing script: start”, without running node)

 我发现它，问题不在于Multi模块Graldle，Spring引导或Oauth2相关。 实际上，这是由于Gradle的src集合配置，其中Java应该位于Java src集文件夹中，而Kotlin位于Java src集文件夹中： 
 
sourceSets {
    main.java.srcDirs += 'src/main/java'
    main.kotlin.srcDirs += 'src/main/kotlin'
}
 
 正如Will Humphreys在他上面的评论中所说的那样，IntelliJ需要所有源代码集并运行该应用程序。 但是，通过Gradle构建jar时，这些源代码集更加严格。 我在我的Kotlin src集合中有一个Java文件，这对IntelliJ来说没有问题。 但是由Gradle创建的jar考虑到了build.gralde文件中定义的源代码集，它们更严格。 
 
 我用下面的代码找到了我的缺失bean问题： 
 
@Bean
public CommandLineRunner commandLineRunner(ApplicationContext ctx) {
    return args -> {
        System.out.println("Let's inspect the beans provided by Spring Boot:");

        String[] beanNames = ctx.getBeanDefinitionNames();
        Arrays.sort(beanNames);
        for (String beanName : beanNames) {
            System.out.println(beanName);
        }

    };
}
 
 我错过的Bean被称为AuthenticationController ，它是一个@RestController ，并且对于我的验证代码至关重要。 

I found it, the problem was not Multi module Graldle, Spring boot, or Oauth2 related. In fact it was due to a src set config of Gradle, where Java was supposed to be in a Java src set folder, and Kotlin in a Java src set folder:
 
sourceSets {
    main.java.srcDirs += 'src/main/java'
    main.kotlin.srcDirs += 'src/main/kotlin'
}
 
As Will Humphreys stated in his comment above, IntelliJ takes all source sets, and runs the app. However, when building the jar via Gradle, these source sets are stricter. I had a Java file in my Kotlin src set, which is no problem for IntelliJ. But the jar created by Gradle takes into account the source sets as defined in the build.gralde file, which are stricter. 
 
I found my missing bean issue with the code below:
 
@Bean
public CommandLineRunner commandLineRunner(ApplicationContext ctx) {
    return args -> {
        System.out.println("Let's inspect the beans provided by Spring Boot:");

        String[] beanNames = ctx.getBeanDefinitionNames();
        Arrays.sort(beanNames);
        for (String beanName : beanNames) {
            System.out.println(beanName);
        }

    };
}
 
The Bean I missed was called AuthenticationController, which is a @RestController, and kinda crucial for my authentication code.