Web应用部署时SCSS等非必要文件的处理最佳实践问询

Great question—this is a common concern when dealing with preprocessor files on PaaS platforms like Heroku. Let's break down your approach and explore better practices:

Your Current Idea: Using postinstall to Delete SCSS Files #

First off, your approach of using a postinstall script to clean up the SCSS folder after compilation is totally workable, but it has tradeoffs you should consider:

• Pros:
  • Super straightforward to implement. Just add a line to your package.json scripts:

    "scripts": {
      "build": "sass src/scss:dist/css",
      "postinstall": "rm -rf src/scss"
    }
    

  • Ties the cleanup directly to your deployment workflow without extra tools.
• Cons:
  • If you ever need to recompile SCSS on Heroku (for debugging or quick tweaks), you'll have no source files left to work with.
  • While Heroku's filesystem is ephemeral (resets on dyno restarts), this still locks you out of on-server adjustments if you need them.

A Better Approach: Integrate Cleanup into Your Build Process #

Instead of postinstall, it's cleaner to bundle SCSS compilation and cleanup into your build script. Here's why:

1. Build steps are the standard place for compilation and asset prep—keeping all these actions grouped makes your workflow easier to debug and maintain.
2. Avoids edge cases where postinstall might run even if your build fails (unlikely, but better safe than sorry).

Example package.json setup:

"scripts": {
  "build:css": "sass src/scss:dist/css",
  "clean:scss": "rm -rf src/scss",
  "build": "npm run build:css && npm run clean:scss"
}

Heroku will automatically run npm run build if it exists in your package.json, so this fits right into the default deployment flow.

Another Angle: Skip Server-Side Compilation Entirely #

If your project allows it, the cleanest solution is to compile SCSS locally (or via a CI/CD tool like GitHub Actions) before deploying to Heroku. Then:

• Add your SCSS source folder to .gitignore so it never gets pushed to Heroku.
• Only commit the compiled CSS files to your repo.

This way, Heroku never sees the SCSS files at all—you're just deploying static assets, which is more efficient and eliminates any need for cleanup on the server.

On Your Mention of a "New Deployment Flow" #

If you're looking to optimize your deployment pipeline further, consider these options:

• Use a dedicated Sass buildpack for Heroku (though npm scripts are usually flexible enough for most projects).
• Implement a CI/CD pipeline that handles building, testing, and cleaning assets before pushing the final bundle to Heroku. This keeps your Heroku environment focused on serving content, not building it.

Final Takeaway #

• If you must compile SCSS on Heroku, moving cleanup to your build script is a more robust alternative to postinstall.
• If you can shift compilation to your local machine or CI, that's the most efficient and low-fuss approach.

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