-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Page works as expected in dev, but not production build #6888
Comments
_.movThe build output animates like it says. |
I'm seeing the same as @lilnasy here. Maybe it was fixed in a patch? Please file a new issue if you have problems. Thanks. |
Thanks for checking. I tried publishing the minimal test case on Netlify and was not able to reproduce the issue. It seems this issue is only reproducible in my local web server (Mongoose v4.1). |
I have similar problem but mine is the javascript is not working on certain pages in build production. but in dev mode its works perfectly. I haven't found a solution yet. Perhaps anyone give me some suggestions? |
I have the same issue. Did you found a fix? |
I am also experiencing the same problem where my site renders fine in development mode, but the css and javascript files could not be loaded in production mode. site: https://main--idyllic-crumble-facf8a.netlify.app/ |
@Albertyhu This is not a bug. Astro does not process You may want to read the documentation for styling. Feel free to create a support thread if you need help. |
@lilnasy Thanks for the suggestion. |
What version of
astro
are you using?2.3.0
Are you using an SSR adapter? If so, which one?
No
What package manager are you using?
npm
What operating system are you using?
Windows
What browser are you using?
Chrome
Describe the Bug
After spending countless hours perfecting our site in dev mode (
astro dev
), we were dismayed to find that many things broke in production (astro build
). Steps to reproduce:astro build
and view the same page in your browser.ISSUE -- The page doesn't load the same as in dev mode (step 1):
https://www.loom.com/share/802aa43daf594ae9b3fc0b71fa444e97
The main reason for this bug report is to point out that the development and production output should be visibly identical so that developers can have confidence that whatever they're building in dev will be reflected accurately in production. I hope the build process can be improved such that either the dev environment also produces the "yoyo" glitch seen in the loom, or the prod environment no longer produces the glitch -- either way is fine as long as both environments produce a consistent output.
Note that I've verified that this issue can be resolved by inlining the CSS, a scenario in which PR #6659 would come in very handy.
Link to Minimal Reproducible Example
https://stackblitz.com/edit/github-y5t9cq
Participation
The text was updated successfully, but these errors were encountered: