Failed to launch dev server on Windows #52

MatteoGauthier · 2021-04-24T18:49:43Z

Got this error

Started Filesystem GraphQL server on port: 4001
Generating Tina config
Cannot find module 'D:\\Dev\\WebDev\\NextJS\\tina-cloud-starter\\.tina\\__generated__\\temp/schema.js'
Require stack:
- D:\Dev\WebDev\NextJS\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\dist\index.js
- D:\Dev\WebDev\NextJS\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\bin\tina-gql, exiting...
D:\Dev\WebDev\NextJS\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\dist\index.js:1
Error: Cannot find module 'D:\\Dev\\WebDev\\NextJS\\tina-cloud-starter\\.tina\\__generated__\\temp/schema.js'
Require stack:
- D:\Dev\WebDev\NextJS\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\dist\index.js
- D:\Dev\WebDev\NextJS\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\bin\tina-gql
    at compile (D:\Dev\WebDev\NextJS\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\dist\index.js:275:22)
    at async FSWatcher.<anonymous> (D:\Dev\WebDev\NextJS\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\dist\index.js:511:9) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    'D:\\Dev\\WebDev\\NextJS\\tina-cloud-starter\\node_modules\\tina-graphql-gateway-cli\\dist\\index.js',
    'D:\\Dev\\WebDev\\NextJS\\tina-cloud-starter\\node_modules\\tina-graphql-gateway-cli\\bin\\tina-gql'
  ]
}
Done in 21.12s.

The text was updated successfully, but these errors were encountered:

DirtyF · 2021-04-26T07:05:45Z

Hi Matteo, thanks for sharing. Please detail what leads to this error, your environment, etc. to give more context. We didn't test under Windows yet 😊

DirtyF · 2021-04-27T17:48:51Z

Problem spotted, fix coming soon :)

logan-anderson · 2021-05-17T12:27:13Z

@MatteoGauthier we had a fix that we thought would resolve the problem but I just tested it and it looks like a new issues has started

Generating Tina config
Cannot find module 'C:\\Users\\Logan\\Documents\\GitHub\\tina-cloud-starter\\.tina\\__generated__\\temp\\schema.js'
Require stack:
- C:\Users\Logan\Documents\GitHub\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\dist\index.js
- C:\Users\Logan\Documents\GitHub\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\bin\tina-gql, exiting...
C:\Users\Logan\Documents\GitHub\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\dist\index.js:1
Error: Cannot find module 'C:\\Users\\Logan\\Documents\\GitHub\\tina-cloud-starter\\.tina\\__generated__\\temp\\schema.js'
Require stack:
- C:\Users\Logan\Documents\GitHub\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\dist\index.js
- C:\Users\Logan\Documents\GitHub\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\bin\tina-gql
    at compile (C:\Users\Logan\Documents\GitHub\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\dist\index.js:275:22)
    at async FSWatcher.<anonymous> (C:\Users\Logan\Documents\GitHub\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\dist\index.js:511:9) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    'C:\\Users\\Logan\\Documents\\GitHub\\tina-cloud-starter\\node_modules\\tina-graphql-gateway-cli\\dist\\index.js',
    'C:\\Users\\Logan\\Documents\\GitHub\\tina-cloud-starter\\node_modules\\tina-graphql-gateway-cli\\bin\\tina-gql'
  ]
}
Done in 23.42s.

any ideas how to fix this one @jeffsee55 ?

DirtyF · 2021-05-17T12:34:53Z

@logan-anderson I still see double slashes in the path, are you using latest version?
Thought tinacms/tina-graphql-gateway#177 would fix the path on Windows.

logan-anderson · 2021-05-17T12:42:26Z

I did npm i tina-graphql-gateway So I thought I would be on the latest

jamespohalloran · 2021-05-17T12:57:11Z

Latest version the CLI too? https://www.npmjs.com/package/tina-graphql-gateway-cli (This might be a dev-dependency)

logan-anderson · 2021-05-17T13:23:01Z

@jamespohalloran Yes tried on the latest version of that as well.

logan-anderson · 2021-05-17T14:25:27Z

I think I tracked down the issue. We are not handling windows when using the fast-glob package should have a fix in soon

logan-anderson · 2021-05-28T12:51:03Z

@MatteoGauthier This should be fixed now on the latest version. Let us know if you run into any more issues and thanks for letting us know about this one.

abrown2644 · 2021-06-08T02:29:17Z

On Windows as well and getting same error currently

yarn run v1.22.10
$ yarn tina-gql server:start -c "next dev"
$ C:\code\practice\tina-cloud-starter\node_modules\.bin\tina-gql server:start -c "next dev"

Started Filesystem GraphQL server on port: 4001
Generating Tina config
Cannot find module 'C:\\code\\practice\\tina-cloud-starter\\.tina\\__generated__\\temp\\schema.js'
Require stack:
- C:\code\practice\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\dist\index.js
- C:\code\practice\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\bin\tina-gql, exiting...
C:\code\practice\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\dist\index.js:1
Error: Cannot find module 'C:\\code\\practice\\tina-cloud-starter\\.tina\\__generated__\\temp\\schema.js'
Require stack:
- C:\code\practice\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\dist\index.js
- C:\code\practice\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\bin\tina-gql
    at compile (C:\code\practice\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\dist\index.js:276:22)
    at async FSWatcher.<anonymous> (C:\code\practice\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\dist\index.js:519:9) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    'C:\\code\\practice\\tina-cloud-starter\\node_modules\\tina-graphql-gateway-cli\\dist\\index.js',
    'C:\\code\\practice\\tina-cloud-starter\\node_modules\\tina-graphql-gateway-cli\\bin\\tina-gql'
  ]
}
Done in 11.50s.

DirtyF · 2021-06-08T07:46:30Z

@abrown2644 What version of the tina-graphql package are you using?

abrown2644 · 2021-06-08T22:10:17Z

@DirtyF I was missing that package actually. Just installed 0.1.12 but same error atm.

logan-anderson · 2021-06-11T12:31:35Z

@abrown2644 I believe the latest version is 0.2.14 can you try yarn add tina-graphql-gateway@latest and then relaunch the dev server?

B-Stewart · 2021-06-14T06:38:38Z

Had to bump to the following to get latest master to work, tina-graphql-gateway wasn't enough. Needed the cli too.

"tina-graphql-gateway-cli": "0.2.45"
"tina-graphql-gateway": "0.2.14"

However, it seems the path it's resolving to isn't correct for non homepage routes. Note the double /content/posts/content/posts

Error: Unable to fetch, errors:
ENOENT: no such file or directory, open 'C:\repos\safely-away-from-the-edge\content\posts\content\posts\voteForPedro.md'

DirtyF · 2021-06-14T08:25:02Z

@B-Stewart right should be content\posts thanks for the feedback. Packages bump is on its way.

B-Stewart · 2021-06-15T03:08:18Z

Opened up a new ticket related to my duplicate path issue as it's kinda related to cross platform path handling, but needs to be fixed in the graphql package tinacms/tina-graphql-gateway#259

DirtyF · 2021-06-15T14:55:56Z

We just released a new version of the package @MatteoGauthier and @B-Stewart please upgrade and tell us if that fixes your issue.

B-Stewart · 2021-06-17T03:56:49Z

Bumping to "tina-graphql-gateway-cli": "0.2.49" now gives me this error using npm

npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported URL Type "workspace:": workspace:packages/tina-graphql-helpers

yarn allows me to choose the package to install instead of crashing

Couldn't find any versions for "tina-graphql-helpers" that matches "workspace:packages/tina-graphql-helpers"
? Please choose a version of "tina-graphql-helpers" from this list: 0.0.22

And the duplicate issue tinacms/tina-graphql-gateway#259 is still happening for me when I get it running again using yarn.

calvary-tucson · 2021-06-19T04:59:05Z

This might be related. Just forked the repository on Windows and ran yarn install and then yarn dev and got this error:

D:\Development\tina-cloud-starter>yarn dev
yarn run v1.22.10
$ yarn tina-gql server:start -c "next dev"
$ D:\Development\tina-cloud-starter\node_modules\.bin\tina-gql server:start -c "next dev"

Started Filesystem GraphQL server on port: 4001
Generating Tina config
Compiling...
Tina config ======> D:\Development\tina-cloud-starter\.tina\__generated__\config
Building schema...
Generating types...
Typescript types => D:\Development\tina-cloud-starter/.tina/__generated__/types.ts
GraphQL types ====> D:\Development\tina-cloud-starter/.tina/__generated__/schema.gql
node:events:355
      throw er; // Unhandled 'error' event
      ^

Error: spawn next ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:282:19)
    at onErrorNT (node:internal/child_process:480:16)
    at processTicksAndRejections (node:internal/process/task_queues:81:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (node:internal/child_process:288:12)
    at onErrorNT (node:internal/child_process:480:16)
    at processTicksAndRejections (node:internal/process/task_queues:81:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn next',
  path: 'next',
  spawnargs: [ 'dev' ]
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

logan-anderson · 2021-06-21T12:31:19Z

@B-Stewart thanks for your report! There was an internal error with the way we where publishing our packages. This should be fixed if you update to the latest versions. I have made a PR that will force this #91.
If you want to upgrade now you can run

yarn upgrade-interactive

and chose all the tina packages.

You can also wait for the PR to me merged and then update your fork.

@calvary-tucson that might be related as well. We will do some internal testing with a windows machine sometime this week. For now you could also try updating and see if the Issue persists.

calvary-tucson · 2021-06-24T05:57:45Z

@logan-anderson
When I click on "Vote for Pedro" I see this error:

The other problem I posted about might has something to do with the script command. I think it has something do to with the "-c" of the "yarn tina-gql server:start -c "next dev"" -- I know if I run the commands separately in different command prompts such as "yarn tina-gql server:start" in one and "yarn next dev" in another. Everything seems like it is working. Not sure if this helps.

Tina Dependencies:
"tina-graphql-gateway-cli": "^0.2.51"
"tina-graphql-gateway": "^0.2.17"
"tinacms": "0.41.0"
"final-form": "4.20.1"

ghowardMSD · 2021-06-29T22:28:16Z

I just forked from main that includes PR #91 and I'm getting this error on Windows unless I split the commands as in previous post :-

$ yarn tina-gql server:start -c "next dev"
$ D:\Projects\Github\tina-cloud-starter\node_modules\.bin\tina-gql server:start -c "next dev"

Started Filesystem GraphQL server on port: 4001
Visit the playground at http://localhost:4001/altair/
Generating Tina config
Compiling...
Transpiling...
Tina config ======> D:\Projects\Github\tina-cloud-starter\.tina\__generated__\config
Done Compiling...
Generating types...
Typescript types => D:\Projects\Github\tina-cloud-starter/.tina/__generated__/types.ts
GraphQL types ====> D:\Projects\Github\tina-cloud-starter/.tina/__generated__/schema.gql
node:events:353
      throw er; // Unhandled 'error' event
      ^

Error: spawn next ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:269:19)
    at onErrorNT (node:internal/child_process:467:16)
    at processTicksAndRejections (node:internal/process/task_queues:80:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (node:internal/child_process:275:12)
    at onErrorNT (node:internal/child_process:467:16)
    at processTicksAndRejections (node:internal/process/task_queues:80:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn next',
  path: 'next',
  spawnargs: [ 'dev' ]
}

jeffsee55 · 2021-06-29T22:35:27Z

@ghowardMSD I think you're running into what @calvary-tucson mentioned, you just need to run those commands in separate windows:

yarn tina-gql server:start

And in another terminal:

yarn next dev

@calvary-tucson I think the issue you're seeing is unrelated to the terminal problem, we're likely just not building that path properly, we'll take a look.

ghowardMSD · 2021-06-29T22:52:00Z

Yes, it does start ok when I run in separate windows and then I get the Pedro path issue.

mitchmac · 2021-07-16T17:56:15Z

Poking at the command issue after someone ran into it while checking out Tina, I tried concurrently and it seemed to work:

"dev": "concurrently \"tina-gql server:start\" \"next dev\""

The order of initial output may be a bit confusing though:

jeffsee55 · 2021-07-16T17:58:35Z

@mitchmac The problem with concurrently is during CI, we wouldn't know when to shut down the GraphQL server. I believe James was playing around with this a while back but I don't think he got it all the way sorted out.

mitchmac · 2021-07-20T17:25:44Z

@jeffsee55 Do we actually need to worry about CI right now for this, if we only changed the "dev" command? CI would be using build & export?

jeffsee55 · 2021-07-20T17:27:16Z

@mitchmac Sure, it's just a pattern. They can also just run two processes.

jeffsee55 · 2021-08-02T16:56:55Z

Related to tinacms/tinacms#1951

ghost · 2021-08-04T09:35:54Z

Concurrently loads the app but renders as 404 and some SSR error using "dev": "concurrently \"tinacms server:start\" \"next dev\"",

logan-anderson · 2021-08-04T14:02:45Z

@mystrdat There was a couple issues with the navigation that have been fixed. Is your Fork up to date with the latest changes in the starter?

ghost · 2021-08-04T14:45:13Z

Yes, I just cloned current main. If i yarn install it and run yarn dev, it stops as it does for #52 (comment)

If I run concurrently \"tinacms server:start\" \"next dev\" it loads but fails with the errors in the image above.
If I add tina-graphql-gateway tina-graphql-gateway-cli packages and run concurrently \"tina-gql server:start\" \"next dev\", it fails as follows

[0] Started Filesystem GraphQL server on port: 4001
[0] Visit the playground at http://localhost:4001/altair/
[1] event - compiled successfully
[0] Generating Tina config
[0] Compiling...
[0] Transpiling...
[0] Cannot read property 'collections' of undefined
[0] tina-gql server:start exited with code 0

logan-anderson · 2021-08-04T14:56:54Z

@mystrdat Thanks for the details. Mind trying concurrently \"tinacms server:start\" \"next dev\ in your scripts instead?

We changed the name of the command to start the server from tina-gql to tinacms

ghost · 2021-08-04T15:36:36Z

I did try those, mentioned them above, that results are in the image I posted. It build but 404s on frontend with the SSR errors.

jeffsee55 · 2021-08-04T16:20:55Z

@mystrdat are you still importing defineSchema from the older tina-graphql-gateway-cli? It should be from @tinacms/cli:

import { defineSchema } from '@tinacms/cli'

ghost · 2021-08-04T16:24:03Z

defineSchema is imported from '@tinacms/cli' as you mention, I'm using the latest main where it is as such. I've only tried tina-graphql-gateway-cli because others mentioned it before but that didn't work either.

jeffsee55 · 2021-08-04T16:28:57Z

Ok just wondering because tina-gql server:start exited with code 0 indicates you're running things with tina-graphql-gateway-cli, tina-gql was our old bin command, tinacms is the new one. The only commands you need are outlined here.

To better debug this, can you run:

yarn tinacms server:start

And checkout `http://localhost:4001/altair. If you see a GraphQL GUI you should be able to run queries on it. That would at least tell us that the GraphQL portion is working.

ghost · 2021-08-04T16:56:04Z

That was from when I tried tina-graphql-gateway-cli, I described that in the comment. http://localhost:4001/altair/ works. The main issue I'm facing when running the current repo main with concurrently is in #52 (comment)

mitchmac · 2021-08-09T16:06:35Z

Per @logan-anderson this should be ok but exposes issues deeper into use

logan-anderson · 2021-08-11T17:58:16Z

The deeper issue should be fixed now as well. Everything should work as expected on windows the same as unix

DirtyF added needs-info windows labels Apr 26, 2021

logan-anderson self-assigned this May 17, 2021

logan-anderson closed this as completed May 17, 2021

logan-anderson reopened this May 17, 2021

DirtyF mentioned this issue Jun 14, 2021

chore(deps): bump tina-graphql-gateway #88

Merged

B-Stewart mentioned this issue Jun 15, 2021

Duplicate content path added in sys { filename } query on windows tinacms/tina-graphql-gateway#259

Open

DirtyF changed the title ~~Failed to launch dev server~~ Failed to launch dev server on Windows Jun 24, 2021

jamespohalloran closed this as completed Sep 21, 2022

Failed to launch dev server on Windows #52

Failed to launch dev server on Windows #52

Comments

MatteoGauthier commented Apr 24, 2021

DirtyF commented Apr 26, 2021 • edited Loading

DirtyF commented Apr 27, 2021

logan-anderson commented May 17, 2021

DirtyF commented May 17, 2021 • edited Loading

logan-anderson commented May 17, 2021

jamespohalloran commented May 17, 2021

logan-anderson commented May 17, 2021

logan-anderson commented May 17, 2021

logan-anderson commented May 28, 2021

abrown2644 commented Jun 8, 2021

DirtyF commented Jun 8, 2021

abrown2644 commented Jun 8, 2021

logan-anderson commented Jun 11, 2021

B-Stewart commented Jun 14, 2021 • edited Loading

DirtyF commented Jun 14, 2021

B-Stewart commented Jun 15, 2021

DirtyF commented Jun 15, 2021

B-Stewart commented Jun 17, 2021

calvary-tucson commented Jun 19, 2021

logan-anderson commented Jun 21, 2021

calvary-tucson commented Jun 24, 2021 • edited Loading

ghowardMSD commented Jun 29, 2021 • edited Loading

jeffsee55 commented Jun 29, 2021

ghowardMSD commented Jun 29, 2021

mitchmac commented Jul 16, 2021

jeffsee55 commented Jul 16, 2021

mitchmac commented Jul 20, 2021

jeffsee55 commented Jul 20, 2021

jeffsee55 commented Aug 2, 2021

ghost commented Aug 4, 2021

logan-anderson commented Aug 4, 2021

ghost commented Aug 4, 2021

logan-anderson commented Aug 4, 2021

ghost commented Aug 4, 2021

jeffsee55 commented Aug 4, 2021

ghost commented Aug 4, 2021 • edited by ghost Loading

jeffsee55 commented Aug 4, 2021

ghost commented Aug 4, 2021 • edited by ghost Loading

mitchmac commented Aug 9, 2021

logan-anderson commented Aug 11, 2021

DirtyF commented Apr 26, 2021 •

edited

Loading

DirtyF commented May 17, 2021 •

edited

Loading

B-Stewart commented Jun 14, 2021 •

edited

Loading

calvary-tucson commented Jun 24, 2021 •

edited

Loading

ghowardMSD commented Jun 29, 2021 •

edited

Loading

ghost commented Aug 4, 2021 •

edited by ghost

Loading

ghost commented Aug 4, 2021 •

edited by ghost

Loading