# Npm install --production

**URL:** https://discourse.nodered.org/t/npm-install-production/19766
**Category:** Dashboard
**Created:** [31 December 2019 03:55 UTC](https://discourse.nodered.org/t/npm-install-production/19766 "2019-12-31T03:55:19Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![iOnline247](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ionline247/32/15634_2.png) [@iOnline247](https://discourse.nodered.org/u/iOnline247)
#### Post date: [31 December 2019 03:55 UTC](https://discourse.nodered.org/t/npm-install-production/19766/1 "2019-12-31T03:55:19Z")

</div>

I installed everything and got it working, but decided to move the `userDir` to something more suitable. I ran an `npm install --production` on the `userDir` to install the modules, but this is now throwing errors in the Debug output:

\<install\_path\>\node-red-dashboard\dist\js\gridstack.min.map not found. Maybe running in dev mode. What can I do to remove this error from the Debug output?

---

<div class="post-metadata">

### Author: ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [31 December 2019 08:32 UTC](https://discourse.nodered.org/t/npm-install-production/19766/2 "2019-12-31T08:32:51Z")

</div>

.map file should only be needed for debug, so I'll need to see why its trying to want it when in production. Don't worry its just a warning, and won't break anything.

---

<div class="post-metadata">

### Author: ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [1 January 2020 16:28 UTC](https://discourse.nodered.org/t/npm-install-production/19766/3 "2020-01-01T16:28:12Z")

</div>

Ah, thanks for raising this.

I managed to totally bork my dev instance just before Christmas and on rebuilding, I installed with --production as well without really thinking through the consequences. I now get warnings like this both in the browser console and on the Node-RED log:

```auto
ui_base - error: { [Error: ENOENT: no such file or directory, stat 'C:\src\nr2\data\node_modules\node-red-dashboard\dist\js\gridstack.min.map']
  errno: -4058,
  code: 'ENOENT',
  syscall: 'stat',
  path:
   'C:\\src\\nr2\\data\\node_modules\\node-red-dashboard\\dist\\js\\gridstack.min.map',
  expose: false,
  statusCode: 404,
  status: 404 }

```

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/b/b7b956a265bef832456bc43e737561a337e41430.png)

As Dave say's it is only a warning but annoying anyway.

---

<div class="post-metadata">

### Author: ![iOnline247](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ionline247/32/15634_2.png) [@iOnline247](https://discourse.nodered.org/u/iOnline247)
#### Post date: [1 January 2020 18:51 UTC](https://discourse.nodered.org/t/npm-install-production/19766/4 "2020-01-01T18:51:58Z")

</div>

Where should I file this as a bug? (I'm guessing on the git repo) `--production` should work without flooding the Debug Console. Before I fixed it, it wasn't that great of an experience debugging.

---

<div class="post-metadata">

### Author: ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [1 January 2020 18:56 UTC](https://discourse.nodered.org/t/npm-install-production/19766/5 "2020-01-01T18:56:34Z")

</div>

Already fixed in master
