asset-manifest.json 404

  • Resolved deandid

    (@lcm404)


    4 years, 1 month ago

    There were several posts that I read that went nowhere regarding the asset-manifest.json 404 in specific plugin support threads so I figured I would post here to get whatever information I can.

    The error is weird in that it only makes itself known when running a Lighthouse report in DevTools (Chrome). 

    (unknown) GET https://mysite.com/asset-manifest.json 404
test
detectLibraries
async function (async)		
detectLibraries
(anonymous)
(anonymous)
Promise.then (async)		
(anonymous)
wrapInNativePromise
(anonymous)

    Anyone have any idea what is up with this thing and how to make sure it doesn’t occur?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator bcworkz

    (@bcworkz)

    Are you using Lighthouse on a site that’s within an IDE? asset-manifest is used by certain IDEs to keep track of its assets. When the site is launched that data doesn’t go along because it’s no longer applicable. Unless you’re seeing that on a production site you can likely ignore it.

    Thread Starter deandid

    (@lcm404)

    Seeing it only in Lighthouse but yes, on a production site. Is this a problem?

    Moderator bcworkz

    (@bcworkz)

    It doesn’t break anything, but it’d be sub-optimal if it occurs in a normal browser. Use the browser’s network developer tool to view a page’s requests. If there are no 404s there, it’s all good.

    Thread Starter deandid

    (@lcm404)

    Thank you!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘asset-manifest.json 404’ is closed to new replies.