@nx/js 20.5.0-beta.0 → 20.5.0-beta.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nx/js",
-  "version": "20.5.0-beta.0",
+  "version": "20.5.0-beta.1",
   "private": false,
   "description": "The JS plugin for Nx contains executors and generators that provide the best experience for developing JavaScript and TypeScript projects. ",
   "repository": {
@@ -39,8 +39,8 @@
     "@babel/preset-env": "^7.23.2",
     "@babel/preset-typescript": "^7.22.5",
     "@babel/runtime": "^7.22.6",
-    "@nx/devkit": "20.5.0-beta.0",
-    "@nx/workspace": "20.5.0-beta.0",
+    "@nx/devkit": "20.5.0-beta.1",
+    "@nx/workspace": "20.5.0-beta.1",
     "@zkochan/js-yaml": "0.0.7",
     "babel-plugin-const-enum": "^1.0.1",
     "babel-plugin-macros": "^3.1.0",

package/src/generators/library/library.js

@@ -63,6 +63,7 @@ async function libraryGeneratorInternal(tree, schema) {
             project: options.name,
             compiler: 'swc',
             format: options.isUsingTsSolutionConfig ? ['esm'] : ['cjs', 'esm'],
+            skipFormat: true,
         });
     }
     if (options.bundler === 'vite') {

package/src/plugins/typescript/plugin.d.ts

@@ -9,6 +9,7 @@ export interface TscPluginOptions {
         buildDepsName?: string;
         watchDepsName?: string;
     };
+    verboseOutput?: boolean;
 }
 /**
  * @deprecated The 'createDependencies' function is now a no-op. This functionality is included in 'createNodesV2'.

package/src/plugins/typescript/plugin.js

@@ -126,11 +126,6 @@ function buildTscTargets(configFilePath, projectRoot, options, context) {
     const targets = {};
     const namedInputs = (0, get_named_inputs_1.getNamedInputs)(projectRoot, context);
     const tsConfig = readCachedTsConfig(configFilePath);
-    // TODO: check whether we want to always run with --pretty --verbose, it makes replacing scripts harder
-    // `--verbose` conflicts with `tsc -b --clean`, might be another reason for not using it, it would
-    // prevent users from running the task with `--clean` flag.
-    // Should we consider creating a different optional target for `--clean`?
-    // Should we consider having a plugin option to disable `--pretty` and `--verbose`?
     let internalProjectReferences;
     // Typecheck target
     if ((0, node_path_1.basename)(configFilePath) === 'tsconfig.json' && options.typecheck) {
@@ -138,7 +133,7 @@ function buildTscTargets(configFilePath, projectRoot, options, context) {
         const externalProjectReferences = resolveShallowExternalProjectReferences(tsConfig, context.workspaceRoot, projectRoot);
         const targetName = options.typecheck.targetName;
         if (!targets[targetName]) {
-            let command = `tsc --build --emitDeclarationOnly --pretty --verbose`;
+            let command = `tsc --build --emitDeclarationOnly${options.verboseOutput ? ' --verbose' : ''}`;
             if (tsConfig.options.noEmit ||
                 Object.values(internalProjectReferences).some((ref) => ref.options.noEmit) ||
                 Object.values(externalProjectReferences).some((ref) => ref.options.noEmit)) {
@@ -174,7 +169,7 @@ function buildTscTargets(configFilePath, projectRoot, options, context) {
         const targetName = options.build.targetName;
         targets[targetName] = {
             dependsOn: [`^${targetName}`],
-            command: `tsc --build ${options.build.configName} --pretty --verbose`,
+            command: `tsc --build ${options.build.configName}${options.verboseOutput ? ' --verbose' : ''}`,
             options: { cwd: projectRoot },
             cache: true,
             inputs: getInputs(namedInputs, configFilePath, tsConfig, internalProjectReferences, context.workspaceRoot, projectRoot),
@@ -584,6 +579,7 @@ function normalizePluginOptions(pluginOptions = {}) {
     return {
         typecheck,
         build,
+        verboseOutput: pluginOptions.verboseOutput ?? false,
     };
 }
 function resolveExtendedTsConfigPath(tsConfigPath, directory) {