Open SalahAdDin opened 1 week ago
Packages affecting at the moment:
yarn why @types/lodash INT ✘
yarn why v1.22.22
[1/4] Why do we have the module "@types/lodash"...?
[2/4] Initialising dependency graph...
warning Resolution field "glob@7.1.6" is incompatible with requested version "glob@^8.0.3"
warning Resolution field "glob@7.1.6" is incompatible with requested version "glob@^10.3.10"
warning Resolution field "glob@7.1.6" is incompatible with requested version "glob@^8.0.3"
warning Resolution field "glob@7.1.6" is incompatible with requested version "glob@^8.1.0"
warning Resolution field "glob@7.1.6" is incompatible with requested version "glob@^7.2.0"
[3/4] Finding dependency...
[4/4] Calculating file sizes...
=> Found "@types/lodash@4.17.9"
info Reasons this module exists
- "@medusajs#admin#@medusajs#admin-ui#react-json-tree" depends on it
- Hoisted from "@medusajs#admin#@medusajs#admin-ui#react-json-tree#@types#lodash"
- Hoisted from "@medusajs#admin#@medusajs#admin-ui#react-json-tree#react-base16-styling#@types#lodash"
info Disk size without dependencies: "3.59MB"
info Disk size with unique dependencies: "3.59MB"
info Disk size with transitive dependencies: "3.59MB"
info Number of shared dependencies: 0
Done in 0.33s.
And
yarn why type-fest ✔
yarn why v1.22.22
[1/4] Why do we have the module "type-fest"...?
[2/4] Initialising dependency graph...
warning Resolution field "glob@7.1.6" is incompatible with requested version "glob@^8.0.3"
warning Resolution field "glob@7.1.6" is incompatible with requested version "glob@^10.3.10"
warning Resolution field "glob@7.1.6" is incompatible with requested version "glob@^8.0.3"
warning Resolution field "glob@7.1.6" is incompatible with requested version "glob@^8.1.0"
warning Resolution field "glob@7.1.6" is incompatible with requested version "glob@^7.2.0"
[3/4] Finding dependency...
[4/4] Calculating file sizes...
=> Found "type-fest@3.13.1"
info Has been hoisted to "type-fest"
info Reasons this module exists
- Hoisted from "@medusajs#admin#@medusajs#admin-ui#type-fest"
- Hoisted from "@medusajs#event-bus-local#@medusajs#utils#@mikro-orm#migrations#umzug#type-fest"
info Disk size without dependencies: "568KB"
info Disk size with unique dependencies: "568KB"
info Disk size with transitive dependencies: "568KB"
info Number of shared dependencies: 0
=> Found "boxen#type-fest@0.20.2"
info This module exists because "@medusajs#medusa#boxen" depends on it.
info Disk size without dependencies: "232KB"
info Disk size with unique dependencies: "232KB"
info Disk size with transitive dependencies: "232KB"
info Number of shared dependencies: 0
=> Found "eslint#type-fest@0.8.1"
info Reasons this module exists
- "eslint#globals" depends on it
- Hoisted from "eslint#globals#type-fest"
info Disk size without dependencies: "112KB"
info Disk size with unique dependencies: "112KB"
info Disk size with transitive dependencies: "112KB"
info Number of shared dependencies: 0
=> Found "ansi-escapes#type-fest@0.21.3"
info This module exists because "jest#@jest#core#ansi-escapes" depends on it.
info Disk size without dependencies: "256KB"
info Disk size with unique dependencies: "256KB"
info Disk size with transitive dependencies: "256KB"
info Number of shared dependencies: 0
Done in 0.30s.
Bug report
Describe the bug
A clear and concise description of what the bug is.
System information
Medusa version (including plugins):
Node.js version: v20.15.1 Database: Postgre SQL 13 Operating system: Manjaro Linux Browser (if relevant): Firefox
Steps to reproduce the behavior
pnpm dlx create-medusa-app@latest
rm -rf node_modules yarn.lock
^
in package.json.yarn
yarn dev
.Expected behavior
It should not give any error.
Screenshots
Code snippets
If applicable, add code samples to help explain your problem
Additional context
When putting the
^
back and removing the lock file, it works properly.