Because Recoil has not getting popular today, so it better to migrate more de facto standard library.

introduce vsc or WebStorem etc..

There is list of plan I have currently.
I don't determined specific quoter for each plans.

• #377
• #523
• #524

when the TodoApp is loaded, the 'NewTodoInput' should set focus.

Original TODO-MVC is not support for smartphone device.
Mainly need replace input, edit interface breakpoint etc.

Sprit from #47

Investigated

Mobile browser does't available on Percy.
Therefore we can only responsible site that simulate Popular SmartPhone's screen size as a Mobile Devices Testing.

Hi. First of all, thanks for this repo.
I noticed you use Prettier.
Could you add your prettier global settings to local file .prettierrc

I'd like to separate role to 'Looks' and 'Layout' onto 2 libraries styled-components and tailwind css.

• styled-components take a 'Looks' that how it looks the component visually such as color, shape, font, size, line-height, border etc
• tailwind css take a 'Layout' such as gird, flex, margin, padding etc

For to do this without breaking style, we should start from create solid visual testing spec on Percy.

hi, thank you for this project,it help me a a lot.I I'm a novice at react, when I try a todo ,so I found there.After some try, I found some problems。
may be bug:

• edit multiple at the same time

• edit todo and then delete its contents. The style will be a little strange after unfocused.

mabe different from TodoMVC:

• can add spaces as todo

• can't always autofocus when edit

they all reappear in your online demo.
many of the above languages come from translation. If my tone is not good, please forgive me.

"React v18 Workgroup" and Twitter, especially Sebastian Markbåge's statements,
have led me to conclude that the CSS-in-JS approach has only disadvantages and no merit to be adopted.

On the other hand, I thought that CSS-Modules,
Tailwind CSS, and Plain CSS as a global style were the most likely candidates for incorporating old-fashioned statically generated CSS into modern development,
so I went with CSS-Modules, which is the most versatile and can be used with Tailwind.
I decided to migrate from the current Styled-Components to CSS-Modules.

Reason of ejected is eslint-loader in webpack that invoke eslint when we yarn start and yarn build.
However that eslint is can't edit from their default config without eject.
But I found override eslint conf feature in the Docs. If it is working fine we can migrate non ejected CRA because we lose reason to eject.
https://create-react-app.dev/docs/setting-up-your-editor#experimental-extending-the-eslint-config

Vite becoming most popular frontend starter tool in the last 6 months.
Vite has actually super fast dev-server and build time so this migrate bring capability that working with fast enough on a low spec environment.

In Stack
reacct router -> react router
:)

Split from #47

Parts

UI logic

login

Might be Cypress can't find out by something dom overlap etc.
Manual test behavior is still clickable and no problem.
So fix it with cypress {force: true} option.

It would be great if it's fully accessible and navigable with keyboard and VO
With your consense can I PR the change @ryota-murakami ?

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• Update dependency @swc/core to v1.3.59
• Update dependency @types/node to v18.16.13
• Update dependency @percy/cli to v1.24.1
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency cypress to v12.12.0
• Update dependency eslint-config-ts-prefixer to ^0.12.0

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• Update dependency @vitejs/plugin-react to v4
• Update dependency rimraf to v5
• Update dependency typescript to v5

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Hello,

We've tried to activate or update your repository on Depfu and couldn't find any supported dependency files. If we were to guess, we would say that this is not actually a project Depfu supports and has probably been activated by error.

Monorepos

Please note that Depfu currently only searches for your dependency files in the root folder. We do support monorepos and non-root files, but don't auto-detect them. If that's the case with this repo, please send us a quick email with the folder you want Depfu to work on and we'll set it up right away!

How to deactivate the project

• Go to the Settings page of either your own account or the organization you've used
• Go to "Installed Integrations"
• Click the "Configure" button on the Depfu integration
• Remove this repo (ryota-murakami/react-typescript-todo-example-2019) from the list of accessible repos.

Please note that using the "All Repositories" setting doesn't make a lot of sense with Depfu.

If you think that this is a mistake

Please let us know by sending an email to [email protected].

This is an automated issue by Depfu. You're getting it because someone configured Depfu to automatically update dependencies on this project.

1.PR
2.CI

• Cypress
• Jest(ReactTestingLibrary)
• Percy
• lint(Prettier & ESLint)
• build
• TypeCheck
• Preview Netlify deploy

Can we replace @reach/router with react-router v6 for the following reasons?

1. @reach/router is an experimental product developed by the same group of developers
2. react-router is the most popular plug-in used by users
3. react-router v6 contains all the functions of @reach/router or even better

Overview

Currently, there is no React perf optimize part.
Excessive optimize is no need for example, even though a few official practice are worth for example.

my strategy is

Analyzing re-render, and then apply performance optimization at some highly cost-effectiveness points.

Overview

refer: https://docs.cypress.io/guides/tooling/code-coverage.html#Instrumenting-code

I have no complaints about Recoil, I think it is a wonderfully maintained library.
There are two things that concern me, that has requirements include integration with Meta's specific technology the Relay.
And the frequency of Breaking Change is too much.