SourceMap error

[niam]

Hi there,

Any ideas why I started getting this error?
I don’t have any map-related elements on the page.

DevTools failed to load SourceMap: Could not parse content for http://localhost:3000/sm/fce9748308f79c28aa5a62ea9d002732d8c4a1c8eaadedab834d5c92787c6fa3.map: Unexpected token < in JSON at position 0
DevTools failed to load SourceMap: Could not load content for http://localhost:3000/bootstrap/4/js/popper.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load SourceMap: Could not load content for http://localhost:3000/bootstrap/4/js/bootstrap.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load SourceMap: Could not parse content for http://localhost:3000/sm/8cfffddf058dc09b67d92f8d849675e6b459dfb8ede5136cf5c98d10acf78cc3.map: Unexpected token < in JSON at position 0

Environment:
Wappler 3.3.1
Node js project
OSX 10.15.6

Thanks!

[karh]

I’m also getting sourcemap errors.
NodeJS, Wappler 3.3.3, Windows 10

[Hyperbytes]

Source map errors are not really errors, they are diagnostic elements only shown in the developers console and they can be ignored. Nothing to worry about, they are quite normal

[karh]

Thanks @Hyperbytes I’ll do some research , quick question before I do so:
can I do something to prevent these errors? Would clean up the console - just an OCD thing…

[Hyperbytes]

i dont think so, they are there for a reason

[patrick]

The source maps are only needed for the developers, it will show the full code instead of the minified version. There are 2 ways to solve the warning.

1. Make sure that you include the source maps, you could get them from the bootstrap website.

2. Turn off the javascript sourcemaps in the devtools.

[karh]

@patrick

Thank you, your one sentence explanation was more clear than my Google research.

Have turned it off for now to keep the console clean. Appreciate it!