Not able to install v7 but i can use v6 without issue about mui-x HOT 5 CLOSED

@LukasTy, thank you for the information. However, we have been using the syntax (variable.?) throughout the project for quite some time, so I suspect the issue stems from something else. The example I provided earlier is just one of many errors originating from the @mui package. I attempted to resolve these by upgrading to webpack 5 and rebuilding the project, which initially seemed to eliminate the errors. Unfortunately, this upgrade led to new issues related to webpack 5 because of other plugins. So we can close this since this is working with webpack 5

from mui-x.

@nethusan, could you check #12612 and the suggested workarounds if you are unable to update to webpack 5?
This issue looks a duplicate of that one, if you agree, feel free to close it. 😉

from mui-x.

@LukasTy I tried that but does not resolve anything, same issue,

this my test from webpack.config

rules: [
	{
		test: /\.[jt]sx?$/,
		exclude: [
			{
				test: path.resolve(__dirname, 'node_modules'),
				exclude: [
					path.resolve(__dirname, 'node_modules/@mui/x-data-grid'),
					path.resolve(__dirname, 'node_modules/@mui/x-license'),
				],
			},
		],
	},
	{
		test: /\.js$|jsx/,
		include: path.resolve(__dirname, '../src'),
		loader: 'babel-loader',
		exclude: [
			{
				test: path.resolve(__dirname, 'node_modules'),
				exclude: [
					path.resolve(__dirname, 'node_modules/@mui/x-data-grid'),
					path.resolve(__dirname, 'node_modules/@mui/x-license'),
				],
			},
		],
		options: {
			cacheDirectory: true,
			cacheCompression: false,
			sourceMaps: true,
			plugins: [
				require.resolve('react-refresh/babel'),
			].filter(Boolean),
		},
	},
	{
		test: /\.(scss|css)$/,
		use: [
			'style-loader',
			'css-loader',
			{
				loader: "sass-loader",
				options: {
					implementation: require("sass"),
				},
			},
		],
		exclude: /node_modules/,
	},
	{
		test: /\.(png|jpg|gif|svg|eot|ttf|woff|woff2)$/,
		loader: 'url-loader',
		options: {
			limit: 10000,
		},
	},
],

Maybe I need to mention that I can see lot more error but similar error message.

from mui-x.

@nethusan I don't see you using the @babel/preset-env, which would include the necessary transforms (i.e. the optional chaining).
Please check this live example for more details.
If it doesn't help, please provide a complete minimal reproduction example.

In any case, I'd strongly advise firstly updating your development setup, then going for the @mui package bumping.
If you add these workarounds, then it's just additional technical debt that can be avoided by switching priorities. 😉

No offense, but isn't it a bit strange having a development setup that doesn't work with features, that have already been live in all major browsers for 4+ years? 🙈

from mui-x.

⚠️ This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.

@nethusan: How did we do? Your experience with our support team matters to us. If you have a moment, please share your thoughts in this short Support Satisfaction survey.

from mui-x.