如何确保 foundation-apps _settings.scss 文件在我 运行 'bower update foundation-apps' 时不被覆盖
How to ensure the foundation-apps _settings.scss file isn't overwritten when I run 'bower update foundation-apps'
我已经通过 bower (bower install foundation-apps) 安装了 Foundation for Apps。
Foundation 说要使用 _settings.scss 进行自定义。但是，当我最终必须更新到最新版本（bower update foundation-apps）时，这个文件不是被覆盖了吗？
您应该将 _settings.scss 文件从 bower_components 目录复制到项目的 scss 文件夹中，这样它就不会在您更新时被覆盖。这是您唯一需要使用的文件。
来自Foundation for Apps Sass Documentation
The Settings File
All Foundatiion projects include a settings file, named _settings.scss. If you're using the CLI to create a Foundation for Apps project, you can find the settings file under client/assets/scss/. If you're installing the framework standalone using Bower or npm, there's a settings file included in those packages, which you can move into your own Sass files to work with.
我已经通过 bower (bower install foundation-apps) 安装了 Foundation for Apps。
Foundation 说要使用 _settings.scss 进行自定义。但是，当我最终必须更新到最新版本（bower update foundation-apps）时，这个文件不是被覆盖了吗？
您应该将 _settings.scss 文件从 bower_components 目录复制到项目的 scss 文件夹中，这样它就不会在您更新时被覆盖。这是您唯一需要使用的文件。
来自Foundation for Apps Sass Documentation
The Settings File
All Foundatiion projects include a settings file, named _settings.scss. If you're using the CLI to create a Foundation for Apps project, you can find the settings file under client/assets/scss/. If you're installing the framework standalone using Bower or npm, there's a settings file included in those packages, which you can move into your own Sass files to work with.