NVM Activation error

When you install nvm latest verion and want to swith the node to use the latest verion , you get the activation error as below: 

>> nvm install 22.13.1 
Installation complete. If you want to use this version, 
type: nvm use 22.13.1 

>> nvm use 22.13.1

 exit status 1: 'C:\Program' is not recognized as an internal or external command, 
operable program or batch file. 
 activation error: exit status 1: 'C:\Program' is not recognized as an internal or external command, operable program or batch file.

This error is happening because your nvm is installed in a path that includes a space (like C:\Program Files\...), and it's not properly handling that space.

Here's how to fix it:

Solution: Reinstall nvm-windows to a path without spaces
Uninstall the current NVM:
Go to Add or Remove Programs and uninstall nvm.

Reinstall NVM to a space-free path:
Download the latest nvm-setup.zip from https://github.com/coreybutler/nvm-windows/releases.
During installation, change the installation path to something like:
Also set the Node.js install path to something like:

After installation, try again:

Alternative (Quick Test, not recommended long-term)
You can temporarily fix this by manually editing your settings.txt file:
Go to:
Update these paths to use short path notation (like C:\Progra~1) or better: move them to a location without spaces.

1. • C:\nvm

   • C:\nodejs
     

2. nvm install 22.13.1
   nvm use 22.13.1

3. C:\Users\<YourUsername>\AppData\Roaming\nvm\settings.txt

Now check this issue, it should work fine,

Implementation of seamless authentication between two Laravel apps

 

When a user logs in to one application, they should also be authenticated in other application without logging in again.

1. Use a Common Authentication System

Ensure both Laravel apps share the same user database (either directly or via API).

---

2. Use tymon/jwt-auth in both apps

Install JWT package in both:

composer require tymon/jwt-auth
php artisan vendor:publish --provider="Tymon\JWTAuth\Providers\LaravelServiceProvider"
php artisan jwt:secret

Do this in both apps. Say App A and App B

---

3. Generate Token in App A on Login

In App A, modify the login logic to generate a JWT token:

use Tymon\JWTAuth\Facades\JWTAuth;

public function login(Request $request)
{
    $credentials = $request->only('email', 'password');

    if (!$token = JWTAuth::attempt($credentials)) {
        return response()->json(['error' => 'Invalid credentials'], 401);
    }

    // Send token to front-end
    return response()->json(['token' => $token]);
}

---

4. Share JWT Token with App B

When user logs in:

1. Save token in a secure cookie:

return response()->json(['success' => true])->cookie(
    'jwt_token', $token, 60, '/', '.seellab.com', true, true, false, 'Strict'
);

✅ This cookie is available to all subdomains, like  App A and App B

2. Alternatively, you can redirect to App B with token in query:

a
https://appbUrl/auth/jwt-login?token=xyz123

---

5. Accept and Authenticate in App B

In AppB, create a route like:

Route::get('/auth/jwt-login', function (Request $request) {
    $token = $request->get('token') ?? $request->cookie('jwt_token');

    try {
        $user = JWTAuth::setToken($token)->authenticate();

        Auth::login($user);

        return redirect('/dashboard'); // or wherever
    } catch (\Exception $e) {
        return redirect('/login')->withErrors('Token Invalid');
    }
});

You can auto-trigger this on page load, or have a middleware that checks and redirects accordingly.

---

6. Keep It Secure

• Use HTTPS.

• Mark cookie as Secure, HttpOnly, and SameSite=Strict if possible.

• Tokens should expire, and refresh tokens can be used optionally.

• If hosting under different domains (not subdomains), cookies won't be shareable — you'll need to redirect with the token.

---

Optional: Middleware in App B

Create a middleware to auto-login using the JWT cookie if user not logged in:

public function handle($request, Closure $next)
{
    if (!Auth::check() && $request->cookie('jwt_token')) {
        try {
            $user = JWTAuth::setToken($request->cookie('jwt_token'))->authenticate();
            Auth::login($user);
        } catch (\Exception $e) {
            // token expired or invalid
        }
    }

    return $next($request);
}

Summary

Feature	Implementation
Token Generation	On login in App A
Token Sharing	Secure Cookie or URL param
Token Reading	App B reads token from cookie/URL
Login Session	Auth::login($user) in App B
Security	HTTPS, HttpOnly, SameSite, Token Expiry