New "dotnet new SAFE" creates files with hardcoded paths to /Users/theimowski/…

[wazum]

E.g.:

app@fable-docker /app % grep -r "theimowski" *
src/Shared/Shared.fs.js.map:{"version":3,"sources":["/Users/theimowski/oss/SAFE-template/Content/default/src/Shared/Shared.fs"],"names":["description","typeName","methodName"],"mappings":";;;;;;;;;;;;;;;;;mCAOiBA;WACgC,CAAzC,mBAA0BA;;;kCAElBA;WACR,oBACgBA
;;;8BAGRC,UAASC;WACjB,OAAQ,OAAA,eAAaD,UAASC","file":null,"sourcesContent":null,"sourceRoot":null}
src/Client/output/App.js.map:{"version":3,"sources":["/Users/theimowski/oss/SAFE-template/Content/default/src/Client/App.fs"],"names":["msg","model","dispatch"],"mappings":";;;;AAsBG,kBALA,6BAA6B,cALhC,\u002BBAA6BA,KAAAC,UAAA,OAAAD,KAAAC,SAAaA,SAAAC,aAAA,
KAAAD,SAAAC","file":null,"sourcesContent":null,"sourceRoot":null}

and so on … and the following npm start produces warnings like

WARNING in ./src/Client/output/App.js
Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from '/Users/theimowski/oss/SAFE-template/Content/default/src/Client/App.fs' file: Error: ENOENT: no such file or directory, open '/Users/theimowski/oss/SAFE-template/Content/default/src/Client/App.fs'

[wazum]

I did start the dev server with npm start instead of using dotnet run … seems to be no problem there