[alpha] Yarn - Incorrect Peer Dependency

[brifiction]

Hello SolidJS,

I have a yarn error (warnings, but vercel builds failed) here, where I've been trying to resolve the incorrect peer dependency, for solid-start@next.

Also, here's my package.json file:

{
  "scripts": {
    ...
  },
  "type": "module",
  "private": true,
  "devDependencies": {
    "solid-app-router": "^0.3.2",
    "solid-js": "^1.3.15",
    "solid-meta": "^0.27.3",
    "solid-start": "next",
    "solid-start-vercel": "next",
    "vite": "^2.9.9"
  },
  "engines": {
    "node": "16.x"
  },
  "dependencies": {
    "axios": "^0.27.2",
    "tachyons": "4.12.0"
  }
}

Can you help? Thank you!

[atk]

This is a known issue that yarn does not work well with version aliases. We can't do much about this warning at the moment; it will vanish once this is released with a proper semver version number.

[brifiction]

Thanks @atk , for taking a look. FYI, I tried npm as well (generated new package-lock.json file, and got the errors below, with screenshots and code block).

FYI, to replicate my initial issue report, the error appears ONLY when I began installing new dependencies - after the Vercel template / boilerplate finished execution that uses yarn.lock, then later cloning the repo to continue work.

And in terminal:

Lastly, in package-lock.json file (please note, version props are same in initial (unmentioned) yarn.lock file at beginning, except for example solid-start@next):

    "solid-start": {
      "version": "0.1.0-alpha.81",
      "resolved": "https://registry.npmjs.org/solid-start/-/solid-start-0.1.0-alpha.81.tgz",
      "integrity": "sha512-+M2qye+GdUdMt/NPoFGuZSb4QKTm4lUoXAf7BchumNP/mybVcecxiytOc6a8M3TWyPC8g8ZxWOXxOs/mWo3GcA==",
      "dev": true,
      "requires": {
        "@babel/core": "^7.16.7",
        "@babel/plugin-syntax-jsx": "^7.16.7",
        "@babel/preset-env": "^7.16.7",
        "@babel/preset-typescript": "^7.16.7",
        "chokidar": "^3.5.3",
        "compression": "^1.7.4",
        "connect": "^3.7.0",
        "cookie": "^0.4.1",
        "cookie-signature": "^1.1.0",
        "debug": "^4.3.4",
        "dequal": "^2.0.2",
        "es-module-lexer": "^0.9.3",
        "esbuild": "^0.14.11",
        "fast-glob": "^3.2.10",
        "parse-multipart-data": "^1.2.1",
        "picocolors": "^1.0.0",
        "rollup": "^2.0.0",
        "rollup-route-manifest": "^1.0.0",
        "sade": "^1.8.0",
        "sirv": "^1.0.19",
        "solid-start-node": "next",
        "undici": "^4.12.2",
        "vite-plugin-inspect": "^0.3.13",
        "vite-plugin-solid": "^2.2.6"
      }
    },
    "solid-start-node": {
      "version": "0.1.0-alpha.74",
      "resolved": "https://registry.npmjs.org/solid-start-node/-/solid-start-node-0.1.0-alpha.74.tgz",
      "integrity": "sha512-dvhlAly3xv+t1IODkDi25oN7Q3sKm0jOV3hqYBE5Y7roDjJaTlZbpSYzZpxc+hdNo5VcdYfiFXff5Xe5V2UILQ==",
      "dev": true,
      "optional": true,
      "requires": {
        "@rollup/plugin-commonjs": "^21.0.1",
        "@rollup/plugin-json": "^4.1.0",
        "@rollup/plugin-node-resolve": "^13.0.2",
        "compression": "^1.7.4",
        "polka": "^1.0.0-next.13",
        "rollup": "^2.53.3",
        "sirv": "^1.0.12"
      }
    },
    "solid-start-vercel": {
      "version": "0.1.0-alpha.81",
      "resolved": "https://registry.npmjs.org/solid-start-vercel/-/solid-start-vercel-0.1.0-alpha.81.tgz",
      "integrity": "sha512-CbVZW3rY8nO7VOuoKlH1+qZ2BCOkaKkQ3VvOMQFQVS7wIz8fkrl5TmXJicJ4s6SVzwYQNXidHiVIKa8DMPLhXA==",
      "dev": true,
      "requires": {
        "@rollup/plugin-commonjs": "^21.0.1",
        "@rollup/plugin-json": "^4.1.0",
        "@rollup/plugin-node-resolve": "^13.0.2",
        "rollup": "^2.53.3",
        "vite": "^2.9.8"
      }
    },

Either way, it was good to try out solidjs's starter. At the moment, I have workarounds in mind.

Keep up the good work, while I stay tuned to solidjs!