PowerBI-visuals-tools: Error: Can't resolve 'process/browser'

@andrewluetgers I also ran into this issue and finally resolved it by adding this to my webpck-config override - I am using react-app-rewired

config.module.rules.push({
      test: /\.m?js/,
      resolve: {
          fullySpecified: false
      }
  })

If you are using a non create-react-app set up you could just addd it to the webpack config like so:

module: {
    rules: [
       {
          test: /\.m?js/,
          resolve: {
              fullySpecified: false
          }
    ]
}

Hope that helps you!

@lucmax94 If you install process as a dev dependency this fixed the problem for me.

Use npm install --save-dev process.

@JipAccobat , so in that case I suppose that the reason of your issue is that now we use webpack version 5+ in powerbi-visuals-tools, and your project dependency lib of webpack is also updated, but starting from version 5 they removed polyfills for Node.js variables. So you need to modify your webpack config a little bit to make it work. Please read articles about migrating to webpack 5.

But as a quick tip, just try to define process in plugins section of your webpack.config.js

const webpack = require("webpack");
...
module.exports = {
...,
    plugins: [
        new webpack.ProvidePlugin({
            process: "process/browser"
        }), ...
    ]
};

@andrewluetgers I also ran into this issue and finally resolved it by adding this to my webpck-config override - I am using react-app-rewired

config.module.rules.push({
      test: /\.m?js/,
      resolve: {
          fullySpecified: false
      }
  })

If you are using a non create-react-app set up you could just addd it to the webpack config like so:

module: {
    rules: [
       {
          test: /\.m?js/,
          resolve: {
              fullySpecified: false
          }
    ]
}

Hope that helps you!

Thanks, that worked perfectly!!

@lucmax94 If you install process as a dev dependency this fixed the problem for me.

Use npm install --save-dev process.

I install this but never worked for me. I am not using webpack.

Still getting the same error as above after upgrading to v3.2.3. I am not using webpack within my project but I tried to fix the error by adding webpack and adding the code from @Demonkratiy. Still getting the same error. Had to go back to v3.1.18.

const webpack = require("webpack");
...
module.exports = {
...,
    plugins: [
        new webpack.ProvidePlugin({
            process: "process/browser"
        }), ...
    ]
};

@lucmax94 If you install process as a dev dependency this fixed the problem for me.

Use npm install --save-dev process.

That worked, thanks!

Hi, I have a similar issue and none of the abobe works for me. Also I cant find Webpack.Config.js Here is my error could anyone help?

ERROR in visual.js Module not found: Error: Can’t resolve ‘C:\Users\gjordan.SPOERERnet\source\repos\Forge2PowerBI\forgePowerbiView.tmp\build\visual.js’ in ‘C:\Users\gjordan.SPOERERnet\source\repos\Forge2PowerBI\forgePowerbiView’
resolve ‘C:\Users\gjordan.SPOERERnet\source\repos\Forge2PowerBI\forgePowerbiView.tmp\build\visual.js’ in ‘C:\Users\gjordan.SPOERERnet\source\repos\Forge2PowerBI\forgePowerbiView’ using description file: C:\Users\gjordan.SPOERERnet\source\repos\Forge2PowerBI\forgePowerbiView\package.json (relative path: .) Field ‘browser’ doesn’t contain a valid alias configuration using description file: C:\Users\gjordan.SPOERERnet\source\repos\Forge2PowerBI\forgePowerbiView\package.json (relative path: ./.tmp/build/visual.js) no extension Field ‘browser’ doesn’t contain a valid alias configuration C:\Users\gjordan.SPOERERnet\source\repos\Forge2PowerBI\forgePowerbiView.tmp\build\visual.js doesn’t exist .tsx Field ‘browser’ doesn’t contain a valid alias configuration C:\Users\gjordan.SPOERERnet\source\repos\Forge2PowerBI\forgePowerbiView.tmp\build\visual.js.tsx doesn’t exist .ts Field ‘browser’ doesn’t contain a valid alias configuration C:\Users\gjordan.SPOERERnet\source\repos\Forge2PowerBI\forgePowerbiView.tmp\build\visual.js.ts doesn’t exist .jsx Field ‘browser’ doesn’t contain a valid alias configuration C:\Users\gjordan.SPOERERnet\source\repos\Forge2PowerBI\forgePowerbiView.tmp\build\visual.js.jsx doesn’t exist .js Field ‘browser’ doesn’t contain a valid alias configuration C:\Users\gjordan.SPOERERnet\source\repos\Forge2PowerBI\forgePowerbiView.tmp\build\visual.js.js doesn’t exist .css Field ‘browser’ doesn’t contain a valid alias configuration C:\Users\gjordan.SPOERERnet\source\repos\Forge2PowerBI\forgePowerbiView.tmp\build\visual.js.css doesn’t exist as directory C:\Users\gjordan.SPOERERnet\source\repos\Forge2PowerBI\forgePowerbiView.tmp\build\visual.js doesn’t exist

webpack 5.74.0 compiled with 1 error in 268 ms Webpack Bundle Analyzer saved report to C:\Users\gjordan.SPOERERnet\source\repos\Forge2PowerBI\forgePowerbiView\webpack.statistics.dev.html assets by status 99 bytes [cached] 1 asset

@andrewluetgers I also ran into this issue and finally resolved it by adding this to my webpck-config override - I am using react-app-rewired

config.module.rules.push({
      test: /\.m?js/,
      resolve: {
          fullySpecified: false
      }
  })

If you are using a non create-react-app set up you could just addd it to the webpack config like so:

module: {
    rules: [
       {
          test: /\.m?js/,
          resolve: {
              fullySpecified: false
          }
    ]
}

Hope that helps you!

Perfect! I wanna hug you.

@JipAccobat @lucmax94 , hi folks! Do you still have this problem on latest version of tools? If so, than please can you tell me if you are using webpack in your projects?