Skip to content

missing jotai-family in node_modules and outdated baseline-browser-mapping #15848

@KadariPavani

Description

@KadariPavani

Describe the bug

Problem

Two dependency issues are currently breaking the dev server and TypeScript checks:

1. jotai-family not resolved at runtime

jotai-family is declared in package.json and package-lock.json but missing
from node_modules, causing Vite and TypeScript to fail on import.

Affected files:

  • src/atoms/navExpansionAtom.ts
  • src/atoms/paymentReconcilationLocationAtom.ts
  • src/atoms/pharmacy.ts

Error:
Failed to resolve import "jotai-family"
Cannot find module 'jotai-family' or its corresponding type declarations.

This happens because jotai-family was added to package.json in a recent
commit but npm install was not re-run, leaving node_modules out of sync
with the lockfile.

2. baseline-browser-mapping is outdated and not declared as a devDependency

The package is a transitive dependency but is over two months old, causing
this warning on every dev server startup:

[baseline-browser-mapping] The data in this module is over two months old.
To ensure accurate Baseline data, please update: npm i baseline-browser-mapping@latest -D

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.


🚨 DO NOT EDIT BELOW THIS LINE 🚨

Instructions for Requesting Assignment:

To request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:

Describe your solution clearly:
Provide a detailed explanation of your proposed solution, including your approach, key implementation steps, and relevant examples or references. Mention any dependencies, assumptions, or risks you foresee that might affect your timeline or implementation.

Expected Timeline:

  • End date: [Expected submission date of a completed Pull Request]

Additional Context:
Include any other relevant context, links, screenshots, or resources that support your proposed solution.

🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions