相似命名的React组件的CSS模块具有冲突样式

如何解决相似命名的React组件的CSS模块具有冲突样式

我最近将Webpack版本从3升级到了4.x。从那以后,我注意到在某些情况下我遇到了一些样式冲突。

例如,我有两个名为PlanCard的不同组件,它们位于应用程序的两个不同目录中。为了简洁起见,假设目录结构类似于以下内容:

- app
+ - Onboarding
  + - OnboardingMembership
    + - PlanCard
      + PlanCard.jsx
      + PlanCard.module.scss 
+ - Settings
  + - ClientSelect
    + - PlanCard
      + PlanCard.jsx
      + PlanCard.module.scss

但是,我发现OnboardingMembership/PlanCard中的样式在应用程序中使用时已应用于ClientSelect/PlanCard。例如,在ClientSelect内正在导入ClientSelect/PlanCard的页面上,我在元素检查器中看到以下内容:

enter image description here

在与该应用程序捆绑在一起的css文件中搜索PlanCard时,我注意到的另一件奇特的事情是:

enter image description here

对我来说最突出的是哈希值。据我所知,这些价值观应该有所不同,我怀疑这就是冲突的根源。

为完整起见,我将包含一些相关的webpack文件。请耐心等待,因为它是一个相当大的应用程序,所以webpack文件被分解成几个文件:

// webpack.dev.js
/* eslint-env node */
const merge = require('webpack-merge')

const common = require('./webpack.common')
const plugins = require('./webpack/plugins')
const outputs = require('./webpack/outputs')
const modules = require('./webpack/modules')

module.exports = merge(common,{
  mode: 'development',devtool: 'cheap-module-source-map',output: outputs.client,module: modules.client,plugins: [...plugins.client,...plugins.clientDev],})

// webpack.common.js

/* eslint-env node */

const { ROOT_PATH,path } = require('./webpack/constants')
const entries = require('./webpack/entries')
const resolves = require('./webpack/resolves')

module.exports = {
  context: path.join(ROOT_PATH,'frontend'),optimization: {
    splitChunks: {
      name: 'common',minChunks: 3,},entry: entries.client,resolve: resolves.client,}
// webpack/plugins.js
'use strict'
/* eslint-env node */

const {
  extractCSSModules,extractCSS,extractCSSModulesProd,extractCSSProd,extractCreatorSCSS,} = require('./constants')

const ManifestPlugin = require('webpack-manifest-plugin')

const plugins = {}

plugins.client = [
  new ManifestPlugin({
    generate: generateManifest,}),]

plugins.clientDev = [
  extractCSS,extractCSSModules,]

plugins.clientProd = [
  extractCSSProd,]


module.exports = plugins

// webpack/outputs.js
'use strict'
/* eslint-env node */

const { path,ROOT_PATH,outputTemplates } = require('./constants')

const outputs = {}

outputs.client = {
  filename: outputTemplates.development.js,chunkFilename: outputTemplates.development.jsChunk,path: path.join(ROOT_PATH,'/public/build'),publicPath: '/build/',}

outputs.clientProd = {
  filename: outputTemplates.production.js,chunkFilename: outputTemplates.production.jsChunk,}

outputs.testUtils = {
  filename: '[name].bundle.js','frontend_build/testUtils'),}

module.exports = outputs
// webpack/module.js
'use strict'
/* eslint-env node */

const MiniCssExtractPlugin = require('mini-css-extract-plugin')

const { path,ROOT_PATH } = require('./constants')

const modules = {}

const isDevelopment = process.env.NODE_ENV === 'development'

modules.client = {
  rules: [
    {
      test: /\.(js|jsx)$/,use: 'babel-loader',exclude: /node_modules/,{
      test: /\.module\.(css|scss)$/,use: [
        isDevelopment ? 'style-loader' : MiniCssExtractPlugin.loader,{
          loader: 'css-loader',query: {
            modules: true,namedExport: true,sourceMap: isDevelopment,camelCase: true,importLoaders: true,localIdentName: '[name]__[local]__[hash:base64:5]',{
          loader: 'postcss-loader',options: {
            plugins: () => [
              require('autoprefixer')({
                browsers: ['> 1%','last 2 versions'],],{ loader: 'sass-loader' },include: path.join(ROOT_PATH,exclude: path.join(ROOT_PATH,'frontend','css'),{
      test: /\.scss$/,{ loader: 'css-loader' },include: '/node_modules/foundation/scss',query: {
            namedExport: true,{
      test: /\.(ttf|eot|svg|woff(2)?)(\?[a-z0-9]+)?$/,use: [
        {
          loader: 'file-loader',options: {
            name: '[name].[hash].[ext]',}

modules.clientProd = {
  rules: [
    {
      test: /\.(js|jsx)$/,options: { modules: true,exportOnlyLocals: true },use: [
        {
          loader: MiniCssExtractPlugin.loader,{ loader: 'style-loader' },}

module.exports = modules
// webpack/constants.js

'use strict'
/* eslint-env node */

const webpack = require('webpack')
const path = require('path')
const MiniCssExtractPlugin = require('mini-css-extract-plugin')

const ROOT_PATH = path.resolve(__dirname,'../../')

const outputTemplates = {
  production: {
    scss: '[name].scss',css: '[name].[hash].css',cssModule: '[name].modules.[hash].css',js: '[name].[hash].js',jsChunk: '[name].chunk.[chunkhash].js',development: {
    scss: '[name].scss',css: '[name].css',cssModule: '[name].modules.css',js: '[name].js',jsChunk: '[name].chunk.js',}

const extractSCSS = new MiniCssExtractPlugin({
  filename: outputTemplates.development.scss,allChunks: true,})

const extractCSSModules = new MiniCssExtractPlugin({
  filename: outputTemplates.development.cssModule,})
const extractCSS = new MiniCssExtractPlugin({
  filename: outputTemplates.development.css,})

const extractCSSModulesProd = new MiniCssExtractPlugin({
  filename: outputTemplates.production.cssModule,})
const extractCSSProd = new MiniCssExtractPlugin({
  filename: outputTemplates.production.css,})

const extractCreatorSCSS = new MiniCssExtractPlugin({
  filename: 'creator.bundle.css',})


module.exports = {
  webpack,path,extractSCSS,outputTemplates,}

如果您仍然与我在一起,我非常感谢您能抽出宝贵的时间给我。我的具体问题是:

  1. 究竟是什么原因导致命名冲突(或没有为具有相同名称的其他组件正确生成新的哈希)?
  2. 应该更改我的配置吗?
  3. 尽管我每天都在使用webpack,但我曾经真正地对其进行过深入研究,以了解其内部知识或最佳实践。如果您发现还有其他可以做得更好的事情,请随时在评论中注明。

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 <select id="xxx"> SELECT di.id, di.name, di.work_type, di.updated... <where> <if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 <property name="dynamic.classpath" value="tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams['font.sans-serif'] = ['SimHei'] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -> systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping("/hires") public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate<String
使用vite构建项目报错 C:\Users\ychen\work>npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-