Closed ruw001 closed 2 years ago
We've restructured the WebGazer package recently to conform better to npm conventions. Take a look, and consider directly using it as an npm package (npm install webgazer
). Alternatively, you could download a local copy of the .js/.js.map file from an older commit in the repo (unsure what point in August you made the project. Did you use npm, did you build from source, or just use the url directly)?
@xanderkoo Hi, thanks for your reply. I directly used the url.
You might consider using this url directly: https://webgazer.cs.brown.edu/webgazer.js .
@Skylion007 Is the minified version / sourcemap currently being hosted on the website?
the .map now lives in the www/ folder, copied automatically on build, via commit https://github.com/brownhci/WebGazer/commit/6a43030a8f8c16784d71f3c66ab8412861971582
I built a prototype using webgazer in August with React and it worked perfect, but now I encountered below warning.
Seems like the file
webgazer.js.map
is missing?