如何移除构建生成的Component-preload.js注释？官方构建工具尝试未果

Been there—trying to slim down your SAPUI5 app's bundle size by stripping comments from Component-preload.js and hitting a wall with the default bestpractice build tool? Let's break down how to get this working, since the built-in uglify in @sap/grunt-sapui5-bestpractice-build doesn't always strip comments as expected.

First: Try Overriding the Bestpractice Build's Uglify Settings #

Chances are, the default config for the sapui5_preload task is set to preserve comments. You can override this directly in your Gruntfile.js to force comment removal:

grunt.config.merge({
  sapui5_preload: {
    component: {
      options: {
        uglify: {
          compress: true,
          mangle: true,
          output: {
            comments: false // This is the key line to strip all comments
          }
        }
      },
      files: {
        // Keep your existing file path here, e.g.:
        "webapp/Component-preload.js": ["webapp/**/*.js", "!webapp/test/**"]
      }
    }
  }
});

This modifies the uglify options that the bestpractice build uses during preload generation, so comments get removed right when the file is created.

If That Fails: Add a Standalone Uglify Post-Task #

If overriding the default config doesn't do the trick, use grunt-contrib-uglify to run a second pass on the generated preload file:

1. Install the plugin first:

npm install grunt-contrib-uglify --save-dev

2. Add the task to your Gruntfile.js:

// Load the plugin
grunt.loadNpmTasks('grunt-contrib-uglify');

// Configure the uglify task for your preload file
grunt.config.merge({
  uglify: {
    stripPreloadComments: {
      options: {
        output: {
          comments: false
        }
      },
      files: {
        // Overwrite the original preload file or output to a new one
        "webapp/Component-preload.js": ["webapp/Component-preload.js"]
      }
    }
  }
});

// Update your build task to run uglify after the preload is generated
grunt.registerTask('build', ['sapui5_preload', 'uglify:stripPreloadComments']);

This takes the preload file the bestpractice build generated and runs a full uglification pass to strip all comments. Just make sure your app's bootstrap points to the right file afterward.

Quick Check: Watch for Global Uglify Configs #

Sometimes your Gruntfile might have a global uglify config that's forcing comments to be preserved. Double-check if there's a top-level uglify section overriding the settings, and adjust that if needed.

Pro tip: If you need to keep license comments (marked with /*! ... */), swap comments: false with comments: 'some'—that way you retain legal comments while stripping all others.

内容的提问来源于stack exchange，提问作者Xnail