Landing-Page | Tailwind CSS Starter Template - Landing Page | Theme library

Just add

There are several reasons why the body tag of your angular app fails to render on the server side. Here's a checklist:

• First make sure your live environment supports NodeJS. Without NodeJS on the server, you can't use server-side rendering
• In Visual Studio, try changing your ASPNETCORE_ENVIRONMENT environment variable from DEVELOPMENT to PRODUCTION and run your application. In some cases the app behaves differently in either configuration (looks for the main.js file in another location when PRODUCTION). After starting the debugger and trying to prerender a view, you may see some exceptions in the Visual Studio Output window.
  • In my case the main.js file had to end up at ClientApp/dist/main.js. So I had to modify angular.json changing the projects:ClientApp:architect:build:options:outputPath to dist (see also)
• If you experience this problem using Visual Studio, do always look at the Output window for errors which will point you in the right direction.
• If you're hosting a PWA (for example through @angular/pwa), then it's totally normal that you're getting an empty page when going to View source in the browser. If you'd then ctrl + F5, you'll be bypassing the angular service worker which shows you the prerendered html source. This is something you shouldn't bother about. Google, Bing, ... will actually fetch and index the server-side rendered version of your page.
• If you're using ASP.NET Core 3.1 or earlier, you cannot have an async lambda for your SupplyData delegate. SupplyData is not a Func and is not being awaited in the source code of ASP.NET Core. I changed this in my port to .NET 6

First, install cross-env

You copy your traefik.yml to /etc/traefik/dynamic.

At startup, Traefik searches for a file named traefik.yml (or traefik.yaml or traefik.toml) in:

• /etc/traefik/
• $XDG_CONFIG_HOME/
• $HOME/.config/
• . (the working directory).

You can override this using the configFile argument, so just add:

Based on your shared code, the reason why window.onscroll does not work as expected is because neither window nor document.body are overflowing vertically. Only the element that is overflowing will fire the scroll event, and in this case it is actually the element that matches the .box-wrapper selector.

Therefore if you listen to the scroll event on that element, then you should be able to retrieve its vertical scroll position using event.currentTarget.scrollTop:

See import statements are case-insensitive on Mac and Windows but case-sensitive on Linux.

Since Gitlab is running linux, try matching the file name exactly

Well, bro!

I tried to make an effort to unscramble the backend code but for now you're posting to the "/api/login" and your html form action is targeting "login".

To make the right call to the post method, change your html to the following action:

Update, I finally fix it. I was being stupid. Turns out that te issue was on my tailwindcss.config.js file! My project structure was different that the one in the tutorial.

├───pages

│ └───api

├───public

├───src

│ ├───components

│ │ ├───footer

│ │ ├───header

│ │ ├───layout

│ │ └───Navigation

│ └───redux

└───styles

After realizing that I notice that my module.exports will never work because my components where on ````src/components```. I simply added the correct file and its now working flawlessly!

Thanks a lot for the help!

The request to advertising image is blocked by the browser, as you can see by opening the dev tools.

In addition, the fact that is working on my mobile phone (screenshot below):

Makes me think that the image is blocked by the browser itself or by some extensions (AdBlock, etc) because of the name to avoid advertisers or publicity by default. Try changing the name of the image or try disabling the extensions.