TODO-App | build awesome products , so we created a set | Runtime Evironment library

When you do myStorage.setItem("todo", JSON.stringify(this.title)), you're saving only the title in localStorage at key "todo". If you later call that same line of code again, you'll be overwriting the value.

If you're saving TODO item titles, they will all need their own key:

myStorage.setItem("todo-key1", todo1.title)

Of you could save them all as a collection:

myStorage.setItem("todos", JSON.stringify([todo1.title, todo2.title]))

but then adding a new todo involves reading the existing value before setting it:

With your current structure why not just make header 10vh and main 90vh. This means that #projects_bar and #tasks_bar will also be 90vh also because 100vh (what you previously had) will cause overflow on the y-axis.

You can also add overflow-y: hidden; on the body to make it not scroll when switching device types.

Edit ~ mentioned in comments, same result without setting a height to the header. Remove all heights, and set height on body to 100vh. min-height: 100vh; is not the same as height: 100vh; so you need to establish that first. Then you can just set height: 100%; to main, and it will fill the remaining viewport.

You have an error in your Secret. If you base64-decode these values:

It is probably a bug. Caz my system not joined to any organization network.

The CA (Certificate Authority) verifies trusted certificates for trusted roots.

Below is the link for repository where you can find the cacert.pem file:

https://github.com/forcedotcom/heroku-cli/blob/master/resources/cacert.pem

Download the file or copy the text and make a new file with same name on your system "cacert.pem"

For example: I have .pem file placed in this location. 'C:\Users\abc\OneDrive\Documents\cacert.pem'.

Now, In 'Environment Variable', add new system variable with below given name and value.

My approche would be like this:

I checked your repo, the problem is here:

In my case this error is usually because of node v17 vs. webpack which usually works fine with node v16.

Did you try Node in version 16 (it is LTS)?

Do not type the action type at all. It is inferred correctly from the type of your asyncThunk if you do nothing at all.

Just to let you know that the tutorial you are following is using firebase web version 8.x, and you could probably have version 9.x installed, as it was pointed out in this comment. In the same question, a user replied that the firebase sdk you need to use is the Firebase admin-sdk.

If this is not the case and you are using the proper SDK versions, then you might need to show how you are importing your dependencies, here the solution was to change the imports.

Also, in the documentation, we can find a warning to constantly update the firebase-functions sdk, as you mentioned that you get the error when using the install firebase command. The warning is:

In many cases, new features and bug fixes are available only with the latest version of the Firebase CLI and the firebase-functions SDK. It's a good practice to frequently update both the Firebase CLI and the SDK with these commands inside the functions folder of your Firebase project: