Scripts: "No entry files discovered in the "src" folder" with entry context in webpack.config.js

[ocean90]

Description

With 21.0.0 of @wordpress/scripts its no longer possible to use the entry context in webpack.config.js because the default config now uses an exit() call in

gutenberg/packages/scripts/utils/config.js

Lines 271 to 274 in 29d123b

	log(
	chalk.bold.red( 'No entry files discovered in the "src" folder.' )
	);
	exit( 1 );

That's quite unfortunate and IMO not necessary. The exit should either be removed or first checked if an entry setting is set in webpack.config.js.

Step-by-step reproduction instructions

1. Create a custom project with @wordpress/scripts
2. Create a webpack.config.js with a custom entry setting
3. Run wp-scripts start

Screenshots, screen recording, code snippet

Example of a webpack config:

const path = require( 'path' );
const defaultConfig = require( './node_modules/@wordpress/scripts/config/webpack.config' );

module.exports = {
	// https://github.com/WordPress/gutenberg/blob/master/packages/scripts/config/webpack.config.js
	...defaultConfig,

	// https://webpack.js.org/configuration/entry-context/#context
	context: path.resolve( __dirname, 'assets/js/src' ),

	// https://webpack.js.org/configuration/entry-context/#entry
	entry: {
		blocks: './blocks.js', // Entry for multiple block imports.
	},

	// https://webpack.js.org/configuration/output/
	output: {
		...defaultConfig.output,
		path: path.resolve( __dirname, 'assets/js/dist' ),
		filename: '[name].js',
	},
};

Environment info

No response

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

[gziolo]

I have a fix ready for review and testing: #38737.

[gziolo]

@wordpress/scripts@21.0.1 is available with the fix.

[shivapoudel]

@gziolo @ocean90 We do have src folder for PHP codes how can I get rid of this message. Still persisting in my environment with version 21.0.1

Why is getWebpackEntryPoints called if I extend the config like this with extending entry:

/**
 * External dependencies
 */
const path = require( 'path' );
const RtlCssPlugin = require( 'rtlcss-webpack-plugin' );

/**
 * WordPress dependencies
 */
const defaultConfig = require( '@wordpress/scripts/config/webpack.config' );

module.exports = {
	...defaultConfig,
	context: path.resolve( __dirname, 'client' ),
	entry: {
		index: './index.js',
	},
	output: {
		...defaultConfig.output,
		chunkFilename: 'chunks/[name].js',
	},
	resolve: {
		...defaultConfig.resolve,
		modules: [ path.join( __dirname, 'client' ), 'node_modules' ],
	},
	plugins: [
		...defaultConfig.plugins,
		new RtlCssPlugin( {
			filename: '[name]-rtl.css',
		} ),
	],
};

[shivapoudel]

@gziolo Can you help me with the ^ comment? Thanks in advance!

[gziolo]

@gziolo Can you help me with the ^ comment? Thanks in advance!

Yes, it still need a fix for your use case. I commented about a potential solution here: #39618 (comment). It’s only a message, your code should work correctly.