A Vue application generated by the v2.0.0 CLI includes registration/login/logout but does not wire email verification or password recovery. Registration creates and logs in the user without sending verification mail.
Verified by generating a disposable Vue application with the CLI rebuilt from exact release commit 3229aa9af542c991196274fa3c235cdce88a68e2:
- The auth controller creates the user, calls Auth::login, and redirects to /dashboard; it does not invoke verification mail delivery.
- Generated routes include login, register, dashboard and logout, but no verification, forgot-password or reset-password routes.
Expected: provide the account-flow routes, pages and framework calls in the scaffold, or make this an explicit scaffold option and clearly document that the basic scaffold omits them. This is a scaffold integration gap, not a claim that the framework lacks account-flow APIs.
Suggested regression: register and capture verification mail; verify a valid link and reject invalid/expired/reused/wrong-owner tokens; request and complete password recovery with appropriate validation feedback. Use captured mail rather than requiring external SMTP.
Verification limit: generated files and released source were inspected; no fresh 2.0.0 mail/browser journey was run. The directory starter already supplies these integrations and tests on its current dependency pin.
Sources:
A Vue application generated by the v2.0.0 CLI includes registration/login/logout but does not wire email verification or password recovery. Registration creates and logs in the user without sending verification mail.
Verified by generating a disposable Vue application with the CLI rebuilt from exact release commit
3229aa9af542c991196274fa3c235cdce88a68e2:Expected: provide the account-flow routes, pages and framework calls in the scaffold, or make this an explicit scaffold option and clearly document that the basic scaffold omits them. This is a scaffold integration gap, not a claim that the framework lacks account-flow APIs.
Suggested regression: register and capture verification mail; verify a valid link and reject invalid/expired/reused/wrong-owner tokens; request and complete password recovery with appropriate validation feedback. Use captured mail rather than requiring external SMTP.
Verification limit: generated files and released source were inspected; no fresh 2.0.0 mail/browser journey was run. The directory starter already supplies these integrations and tests on its current dependency pin.
Sources: