webpack generates error when run in a directory starting with an exclamation sign #6742

doberkofler · 2018-03-13T16:51:43Z

Do you want to request a feature or report a bug?
bug

What is the current behavior?
Using webpack in a directory start starts with !, generates errors but works as expected when the directory does not start with !


D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test>npm run build

> [email protected] build D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test
> webpack --progress --display-error-details

Hash: 03eec963e3df63b69ec7
Version: webpack 3.11.0
Time: 3824ms
   Asset     Size  Chunks             Chunk Names
index.js  7.37 kB       0  [emitted]  index
   [0] ./src/index.js 21 bytes {0} [built]
   [1] ./src/index.css 4.48 kB {0} [built] [failed] [1 error]

ERROR in ./src/index.css
Module build failed: EntryModuleNotFoundError: Entry module not found: Error: Can't resolve 'test\src\index.css' in 'D:\MyDev\ljs_app\trunk\periscope\examples\w
ebpack\!test\src'
    at moduleFactory.create (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\webpack\lib\Compilation.js:411:30)
    at factory (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\webpack\lib\NormalModuleFactory.js:237:20)
    at resolver (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\webpack\lib\NormalModuleFactory.js:60:20)
    at asyncLib.parallel (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\webpack\lib\NormalModuleFactory.js:127:20)
    at D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\async\dist\async.js:3874:9
    at D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\async\dist\async.js:473:16
    at iteratorCallback (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\async\dist\async.js:1048:13)
    at D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\async\dist\async.js:958:16
    at D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\async\dist\async.js:3871:13
    at resolvers.normal.resolve (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\webpack\lib\NormalModuleFactory.js:119:22)
    at onError (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\enhanced-resolve\lib\Resolver.js:65:10)
    at loggingCallbackWrapper (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\enhanced-resolve\lib\createInnerCallback.js:31:19)
    at runAfter (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\enhanced-resolve\lib\Resolver.js:158:4)
    at innerCallback (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\enhanced-resolve\lib\Resolver.js:146:3)
    at loggingCallbackWrapper (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\enhanced-resolve\lib\createInnerCallback.js:31:19)
    at next (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\tapable\lib\Tapable.js:252:11)
    at D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\enhanced-resolve\lib\UnsafeCachePlugin.js:40:4
    at loggingCallbackWrapper (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\enhanced-resolve\lib\createInnerCallback.js:31:19)
    at runAfter (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\enhanced-resolve\lib\Resolver.js:158:4)
    at innerCallback (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\enhanced-resolve\lib\Resolver.js:146:3)
    at loggingCallbackWrapper (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\enhanced-resolve\lib\createInnerCallback.js:31:19)
    at next (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\tapable\lib\Tapable.js:252:11)
    at innerCallback (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\enhanced-resolve\lib\Resolver.js:144:11)
    at loggingCallbackWrapper (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\enhanced-resolve\lib\createInnerCallback.js:31:19)
    at next (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\tapable\lib\Tapable.js:249:35)
    at resolver.doResolve.createInnerCallback (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\enhanced-resolve\lib\DescriptionFilePlugin.j
s:44:6)
    at loggingCallbackWrapper (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\enhanced-resolve\lib\createInnerCallback.js:31:19)
    at afterInnerCallback (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\enhanced-resolve\lib\Resolver.js:166:11)
    at loggingCallbackWrapper (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\enhanced-resolve\lib\createInnerCallback.js:31:19)
    at next (D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\tapable\lib\Tapable.js:249:35)
 @ ./src/index.css
 @ ./src/index.js

ERROR in ./src/index.css
Module not found: Error: Can't resolve 'test/node_modules/css-loader/lib/css-base.js' in 'D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\src'
resolve 'test/node_modules/css-loader/lib/css-base.js' in 'D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\src'
  Parsed request is a module
  using description file: D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\package.json (relative path: ./src)
    Field 'browser' doesn't contain a valid alias configuration
  after using description file: D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\package.json (relative path: ./src)
    resolve as module
      D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\src\node_modules doesn't exist or is not a directory
      D:\MyDev\ljs_app\trunk\periscope\examples\webpack\node_modules doesn't exist or is not a directory
      D:\MyDev\ljs_app\trunk\periscope\examples\node_modules doesn't exist or is not a directory
      D:\MyDev\ljs_app\trunk\periscope\node_modules doesn't exist or is not a directory
      D:\MyDev\ljs_app\trunk\node_modules doesn't exist or is not a directory
      D:\MyDev\ljs_app\node_modules doesn't exist or is not a directory
      D:\MyDev\node_modules doesn't exist or is not a directory
      D:\node_modules doesn't exist or is not a directory
      looking for modules in D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules
        using description file: D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\package.json (relative path: ./node_modules)
          Field 'browser' doesn't contain a valid alias configuration
        after using description file: D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\package.json (relative path: ./node_modules)
          using description file: D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\package.json (relative path: ./node_modules/test/node_modules/css-load
er/lib/css-base.js)
            no extension
              Field 'browser' doesn't contain a valid alias configuration
              D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\test\node_modules\css-loader\lib\css-base.js doesn't exist
            .js
              Field 'browser' doesn't contain a valid alias configuration
              D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\test\node_modules\css-loader\lib\css-base.js.js doesn't exist
            .json
              Field 'browser' doesn't contain a valid alias configuration
              D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\test\node_modules\css-loader\lib\css-base.js.json doesn't exist
            as directory
              D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\test\node_modules\css-loader\lib\css-base.js doesn't exist
[D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\src\node_modules]
[D:\MyDev\ljs_app\trunk\periscope\examples\webpack\node_modules]
[D:\MyDev\ljs_app\trunk\periscope\examples\node_modules]
[D:\MyDev\ljs_app\trunk\periscope\node_modules]
[D:\MyDev\ljs_app\trunk\node_modules]
[D:\MyDev\ljs_app\node_modules]
[D:\MyDev\node_modules]
[D:\node_modules]
[D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\test\node_modules\css-loader\lib\css-base.js]
[D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\test\node_modules\css-loader\lib\css-base.js.js]
[D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\test\node_modules\css-loader\lib\css-base.js.json]
[D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\test\node_modules\css-loader\lib\css-base.js]
 @ ./src/index.css 1:27-88
 @ ./src/index.js
Child extract-text-webpack-plugin ..!test\node_modules\extract-text-webpack-plugin\dist ..!test\node_modules\css-loader\index.js??ref--1-1!..!test\src\index.css
:

    ERROR in Entry module not found: Error: Can't resolve 'test\src\index.css' in 'D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\src'
    resolve 'test\src\index.css' in 'D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\src'
      Parsed request is a module
      using description file: D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\package.json (relative path: ./src)
        Field 'browser' doesn't contain a valid alias configuration
      after using description file: D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\package.json (relative path: ./src)
        resolve as module
          D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\src\node_modules doesn't exist or is not a directory
          D:\MyDev\ljs_app\trunk\periscope\examples\webpack\node_modules doesn't exist or is not a directory
          D:\MyDev\ljs_app\trunk\periscope\examples\node_modules doesn't exist or is not a directory
          D:\MyDev\ljs_app\trunk\periscope\node_modules doesn't exist or is not a directory
          D:\MyDev\ljs_app\trunk\node_modules doesn't exist or is not a directory
          D:\MyDev\ljs_app\node_modules doesn't exist or is not a directory
          D:\MyDev\node_modules doesn't exist or is not a directory
          D:\node_modules doesn't exist or is not a directory
          looking for modules in D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules
            using description file: D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\package.json (relative path: ./node_modules)
              Field 'browser' doesn't contain a valid alias configuration
            after using description file: D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\package.json (relative path: ./node_modules)
              using description file: D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\package.json (relative path: ./node_modules/test/src/index.css)
                no extension
                  Field 'browser' doesn't contain a valid alias configuration
                  D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\test\src\index.css doesn't exist
                .js
                  Field 'browser' doesn't contain a valid alias configuration
                  D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\test\src\index.css.js doesn't exist
                .json
                  Field 'browser' doesn't contain a valid alias configuration
                  D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\test\src\index.css.json doesn't exist
                as directory
                  D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test\node_modules\test\src\index.css doesn't exist
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! [email protected] build: `webpack --progress --display-error-details`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\doberkofler.LBITS\AppData\Roaming\npm-cache\_logs\2018-03-13T16_50_39_385Z-debug.log

D:\MyDev\ljs_app\trunk\periscope\examples\webpack\!test>

If the current behavior is a bug, please provide the steps to reproduce.
just run webpack --progress --display-error-details in a directory that starts with an exclamation sign.

minimal reproduceable repo:
https://github.com/doberkofler/webpack_issue_6742

webpack.config.js:

'use strict';

const path = require('path');
const webpack = require('webpack');
const ExtractTextPlugin = require('extract-text-webpack-plugin');

module.exports = function config(env) {
	return {
		entry: {
			index: './src/index.js'
		},
		output: {
			path: path.resolve(__dirname, 'dist'),
			filename: '[name].js'
		},
		module: {
			rules: [
				{
					test: /\.js$/i,
					include: /src/,
					exclude: /node_modules/,
					use: {
						loader: 'babel-loader'
					}
				},
				{
					test: /\.css$/i,
					include: /src/,
					exclude: /node_modules/,
					use: ExtractTextPlugin.extract([{
						loader: 'css-loader',
						options: {
							sourceMap: false
						}
					}])
				}
			]
		},
		plugins: [
			new ExtractTextPlugin('[name].css')
		]
	};
};

What is the expected behavior?
webpack should not fail or at least report that it cannot be used in certain directories.

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.
node: v8.10.0
webpack: 3.11.0

The text was updated successfully, but these errors were encountered:

chengluyu · 2018-03-14T02:04:44Z

Simply remove exclamation sign from your directory name because it's a part of loader syntax:

Loaders are activated by using loadername! prefixes in require() statements, or are automatically applied via regex from your webpack configuration – see configuration.

doberkofler · 2018-03-14T04:59:53Z

As written in my problem description I do obviously undertsand that the exclamation sign is the problem but:p it took me several hours to find out and I wanted to keep others from falling into the same trap.

why is it the problem (I understand the files but not the directory) ?
does the error message in any way help me to detect this problem ?
couldn’t webpack warn me when just starting a build ?

chengluyu · 2018-03-14T06:08:39Z

@doberkofler
Because internally webpack use absolute paths. Before you, other people had encountered the same problem. See #5320.

doberkofler · 2018-03-14T08:35:04Z

@chengluyu I see. This actually strongly suggests that webpack should really check for an unsupported project directory name and give a proper error message.

sokra · 2018-03-14T09:22:53Z

We could add a schema validation error when somebody passes an path with ! as absolute path in the config.

This could be added to the custom absolutePath schema validator in schemas. Send a PR.

byzyk · 2018-03-14T10:59:12Z

I can have a look at it

doberkofler · 2018-03-14T11:13:33Z

@sokra Unfortunately I do not have the needed webpack knowledge to do a PR myself.

chengluyu · 2018-03-14T11:39:36Z

@byzyk I'm working on it. I added an extra check before this line.

doberkofler · 2018-03-21T08:20:24Z

Thank you all!

ooflorent added the Send a PR label Mar 14, 2018

byzyk mentioned this issue Mar 14, 2018

fix: validation error when ! is in the path #6754

Merged

1 task

chengluyu mentioned this issue Mar 15, 2018

add check for exclamation mark in absolute path #6761

Closed

sokra closed this as completed in #6754 Mar 21, 2018

shahar-h mentioned this issue May 12, 2020

Fix: Plugins folders are created with exclamation mark, which breaks webpack eclipse-theia/theia#7799

Merged

1 task

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

webpack generates error when run in a directory starting with an exclamation sign #6742

webpack generates error when run in a directory starting with an exclamation sign #6742

doberkofler commented Mar 13, 2018 •

edited

Loading

chengluyu commented Mar 14, 2018 •

edited

Loading

doberkofler commented Mar 14, 2018

chengluyu commented Mar 14, 2018

doberkofler commented Mar 14, 2018

sokra commented Mar 14, 2018

byzyk commented Mar 14, 2018

doberkofler commented Mar 14, 2018

chengluyu commented Mar 14, 2018

doberkofler commented Mar 21, 2018

webpack generates error when run in a directory starting with an exclamation sign #6742

webpack generates error when run in a directory starting with an exclamation sign #6742

Comments

doberkofler commented Mar 13, 2018 • edited Loading

chengluyu commented Mar 14, 2018 • edited Loading

doberkofler commented Mar 14, 2018

chengluyu commented Mar 14, 2018

doberkofler commented Mar 14, 2018

sokra commented Mar 14, 2018

byzyk commented Mar 14, 2018

doberkofler commented Mar 14, 2018

chengluyu commented Mar 14, 2018

doberkofler commented Mar 21, 2018

doberkofler commented Mar 13, 2018 •

edited

Loading

chengluyu commented Mar 14, 2018 •

edited

Loading