Field 'browser' doesn't contain a valid alias configuration

Just for record, because I had similiar problem, and maybe this answer will help someone: in my case I was using library which was using .js files and I didn't had such extension in webpack resolve extensions. Adding proper extension fixed problem:

module.exports = {
  // ...
  resolve: {
    extensions: ['.ts', '.js'],
  }
}

I'm building a React server-side renderer and found this can also occur when building a separate server config from scratch. If you're seeing this error, try the following:

1. Make sure your entry value is properly pathed relative to your context value. Mine was missing the preceeding ./ before the entry file name.
2. Make sure you have your resolve value included. Your imports on anything in node_modules will default to looking in your context folder, otherwise.

Example:

const serverConfig = {
name: 'server',
context: path.join(__dirname, 'src'),
entry: {serverEntry: ['./server-entry.js']},
output: {
    path: path.join(__dirname, 'public'),
    filename: 'server.js',
    publicPath: 'public/',
    libraryTarget: 'commonjs2'
},
module: {
    rules: [/*...*/]
},
resolveLoader: {
    modules: [
        path.join(__dirname, 'node_modules')
    ]
},
resolve: {
    modules: [
        path.join(__dirname, 'node_modules')
    ]
}
};

I encountered this error in a TypeScript project. In my webpack.config.js file I was only resolving TypeScript files i.e.

resolve: {
    extensions: [".ts"],
}

However I noticed that the node_module which was causing the error:

Field 'browser' doesn't contain a valid alias configuration

did not have any ".ts" files (which is understandable as the module has been converted to vanilla JS. Doh!).

So to fix the issue I updated the resolve declaration to:

resolve: {
    extensions: [".ts", ".js"],
}

I had the same issue, but mine was because of wrong casing in path:

// Wrong - uppercase C in /pathCoordinate/
./path/pathCoordinate/pathCoordinateForm.component

// Correct - lowercase c in /pathcoordinate/
./path/pathcoordinate/pathCoordinateForm.component

Add this to your package.json:

"browser": {
  "[module-name]": false   
},

This also occurs when the webpack.config.js is simply missing (dockerignore 🤦‍♂️)

In my case it was a package that was installed as a dependency in package.json with a relative path like this:

"dependencies": {
  // ...
  "phoenix_html": "file:../deps/phoenix_html"
},

and imported in js/app.js with import "phoenix_html"

This had worked but after an update of node, npm, etc... it failed with the above error-message.

Changing the import line to import "../../deps/phoenix_html" fixed it.

I changed my entry to:

entry: path.resolve(__dirname, './src/js/index.js'),

and it worked.

I had aliases into tsconfig.json:

{
  "compilerOptions": {
    "paths": {
      "@store/*": ["./src/store/*"]
    }
  },
}

So I solved this issue by adding aliases to webpack.config also:

module.exports = {
  //...
  resolve: {
    alias: {
      '@store': path.resolve(__dirname, '../src/store'),
    },
  },
};

I was getting the same error and I didn't want absolute imports. My normal relative import was not working with the same error and "module not found".

I was missing this in my webpack config.

resolve: {
  extensions: ['.tsx', '.ts', '.js'],
}

My case was rather embarrassing: I added a typescript binding for a JS library without adding the library itself.

So if you do:

npm install --save @types/lucene

Don't forget to do:

npm install --save lucene

Kinda obvious, but I just totally forgot and that cost me quite some time.

I got same problem and fixed with adding file extension.

// Old:
import RadioInput from './components/RadioInput'

// New:
import RadioInput from './components/RadioInput.vue'

Also, if you still want to use without extensions, you can add this webpack config: (Thanx for @matthew-herbst for the info)

module.exports = {
  //...
  resolve: {
    extensions: ['.js', '.json', '.wasm'], // Add your extensions here.
  },
};

In my case, it was due to a broken symlink when trying to npm link a custom angular library to consuming app. After running npm link @authoring/canvas

"@authoring/canvas": "path/to/ui-authoring-canvas/dist"

It appear everything was OK but the module still couldn't be found:

When I corrected the import statement to something that the editor could find Link:

import {CirclePackComponent} from '@authoring/canvas/lib/circle-pack/circle-pack.component';

I received this which is mention in the overflow thread:

To fix this I had to:

1. cd /usr/local/lib/node_modules/packageName
2. cd ..
3. rm -rf packageName
4. In the root directory of the library, run:

a) rm -rf dist
b) npm run build
c) cd dist 
d) npm link

5. In the consuming app, update the package.json with:

"packageName": "file:/path/to/local/node_module/packageName""

6. In the root directory of the consuming app run npm link packageName

In my case, to the very end of the webpack.config.js, where I should exports the config, there was a typo: export(should be exports), which led to failure with loading webpack.config.js at all.

const path = require('path');

const config = {
    mode: 'development',
    entry: "./lib/components/Index.js",
    output: {
        path: path.resolve(__dirname, 'public'),
        filename: 'bundle.js'
    },
    module: {
        rules: [
            {
                test: /\.js$/,
                loader: 'babel-loader',
                exclude: path.resolve(__dirname, "node_modules")
            }
        ]
    }
}

// pay attention to "export!s!" here
module.exports = config;

For anyone building an ionic app and trying to upload it. Make sure you added at least one platform to the app. Otherwise you will get this error.

In my experience, this error was as a result of improper naming of aliases in Webpack. In that I had an alias named redux and webpack tried looking for the redux that comes with the redux package in my alias path.

To fix this, I had to rename the alias to something different like Redux.

In my case (lolz),

I was importing a local package (that I was developing, and building with rollup) via NPM/Yarn link, into another package I was developing. The imported package was a load of React components, and was configured to have a peerDependency of react and react-dom.

The consuming package was being built with Webpack and obviously wasn't correctly feeding the installed react and react-dom libraries into my local dependency as it was compiling it.

I adjusted my webpack configuration to indicate it should alias those peer dependencies to the correct dependencies in the consuming package:

/* ... */

resolve: {
  extensions: [/* make sure you have them all correct here, as per other answers */],
  alias: {
    react: path.resolve('./node_modules/react'),
    'react-dom': path.resolve('./node_modules/react-dom')
  }
},

/* ... */

Obviously you need to import path in the webpack.config.js file in order to use the methods seen above.

A more detailed explanation can be found in this article

In my case I had accidentally imported this package while trying to use process.env:

import * as process from 'process';

Removing it fixed the problem.

A possible reason, would be, if you have nullified a certain dependency in webpack.config.js:

resolve: {
    fallback: {
        fs: false,
        path: false,
    },
},

You also need to add to package.json:

"browser": {
    "fs": false,
    "path": false,
}, 

I solved that issue by adding an extensionAlias property in webpack.config.js:

resolve: {
  extensions: [".ts", ".tsx", ".js"],
  extensionAlias: {
    ".js": [".js", ".ts"],
    ".cjs": [".cjs", ".cts"],
    ".mjs": [".mjs", ".mts"]
  }
},

In my case I was using invalid templateUrl.By correcting it problem solved.

@Component({
        selector: 'app-edit-feather-object',
        templateUrl: ''
    })

My case was similar to @witheng's answer.

At some point, I noticed some casing error in some file names in my development environment. For example the file name was

type.ts

and I renamed it to

Type.ts

In my Mac dev environment this didn't register as a change in git so this change didn't go to source control.

In the Linux-based build machine where the filenames are case-sensitive it wasn't able to find the file with different casing.

To avoid issues like this in the future, I ran this command in the repo:

git config core.ignorecase false

In my case, I imported library files like:

import { MyFile } from "my-library/public-api";

After I removed the public-api from the import everything worked fine:

import { MyFile } from "my-library";

MyFile is exported in the public-api file in the library.

I was getting this error when running a GitHub action. The issue was because I'd listed the package as a peer dependency instead of a dependency.

Since I'm using Rollup, the solution was to install the package both as a peer dependency and a dev dependency, and use rollup-plugin-peer-deps-external to remove the dev dependency from the final build.

For me the issue was, I was importing

.ts files into .js files

changing them to ts as well solved the issue.

In my case, I had a mixture of enum and interface in the index.d.ts file.
I extracted enums into another file and the issue resolved.

In my case, entry field was missing under module.exports in webpack.config.js, causing this issue.

In my case,

I have mistakenly removed a library ("mini-create-react-context") from package.json. I added that back, and did yarn install and build the app and it start working properly. So please take a look at your package.json file once.

For anyone using Webpack's Module Federation plugin:
I had a typo in the value of one of the fileds in the 'exposes' entry of the plugin.
Check your spelling:

exposes: {
            './ShopApp': './src/bootstrap' // check this value
        }