AnsweredAssumed Answered

Problems building 2.0.0-beta.6

Question asked by anthony.colby@cgi.com on Dec 1, 2015
Latest reply on Dec 1, 2015 by JGravois-esristaff

Okay, I'm a bit new to this but I don't think I'm going wildly wrong - hopefully.

 

I'm looking to get Esri Leaflet to support an internal custom cached map scales and therefore am modifying the TileLayer code. I've forked and cloned a copy of the 2.0.0-beta.6 code base from Git, have made the changes I want to test, but am struggling to get the build process to work.

 

The process I've followed is:

 

  • The current user is a local administrator - PC is running Windows 10 but I've had the same issue on a Windows 7 PC.
  • I've downloaded and installed the latest versions of Node.js and GItHub Desktop.
  • I've forked and cloned the code base to my local machine and at this stage haven't made any changes to the code base (I want to make sure I can get the build process working first before making changes and running it again).
  • In GitHub Desktop I've opened a 'Git Shell' and run 'npm install', but get the following output:

 

C:\GitHub\esri-leaflet [master]> npm install

/

> esri-leaflet@2.0.0-beta.6 prepublish C:\GitHub\esri-leaflet

> npm run build

> esri-leaflet@2.0.0-beta.6 prebuild C:\GitHub\esri-leaflet

> mkdirp dist

> esri-leaflet@2.0.0-beta.6 build C:\GitHub\esri-leaflet

> ./scripts/build.js

'.' is not recognized as an internal or external command,

operable program or batch file.

 

Once the build successfully completes then I'm expecting to run 'npm run serve' and then 'npm test' - is that correct?

 

Any suggestions / help would be appreciated.

 

Thanks

 

Tony

Outcomes