Skip to content
This repository has been archived by the owner on Oct 30, 2022. It is now read-only.

deprecated warnings during install #62

Closed
umsaenga opened this issue May 15, 2020 · 11 comments
Closed

deprecated warnings during install #62

umsaenga opened this issue May 15, 2020 · 11 comments
Labels
help wanted Extra attention is needed

Comments

@umsaenga
Copy link

Hello - trying to install and use ghost theme. During install I received errors relating to being deprecated.

npm WARN deprecated core-js@2.6.11: [...]
npm WARN deprecated request@2.88.2: [...]
npm WARN deprecated @babel/polyfill@7.8.7: [...]
npm WARN deprecated chokidar@2.1.8: [...]
npm WARN deprecated fsevents@1.2.13: [...]
npm WARN deprecated resolve-url@0.2.1: [...]
npm WARN deprecated urix@0.1.0: [...]

Later when I try to develop I get several more warnings and errors (attached) and not being able to develop.

Are the deprecated warning issues causing the later ones? I tried to search around and couldn't find many answers.

Thank you

ghostErrorsFull.txt

ERROR #98123 WEBPACK [...]
warn There are multiple modules with names that only differ in casing. [...]
the full output is attached.

@umsaenga
Copy link
Author

Forgot to mention that I did look through this thread #10. and still received error

@styxlab
Copy link
Owner

styxlab commented May 15, 2020

These are all very strange errors. I don't have a solution, but some pointers, that may help you:

  1. Before using gatsby-theme-try-ghost you should start with gatsby-starter-try-ghost and see if you can get it compiled. The starter s a user version whereas the theme is for developers.

  2. Make sure you start from a fresh clone. I see some very strange messages indicating that you are not running the latest version or made modifications to the code yourself.

  3. I see that you directly use gatsby develop, but you should use yarn develop as the theme is setup as a monorepo with workspaces that are only correctly handled with yarn.

  4. Before using yarn develop, make sure to issue yarn, so all packages are updated correctly. Do not mix npm and yarn, only use yarn with this repo.

  5. Looks like you are using windows OS which is not supported. Try using it on linux if you can.

  6. Especially the webpack failures are indicating a general problem with your OS/gatsby/react setup.

  7. Depreciation warnings can usually be ignored and are not causing the compile to fail.

Let me know, if you get it to work. I keep my fingers crossed!

@umsaenga
Copy link
Author

umsaenga commented May 15, 2020

  1. I thought I did use starter try ghost. tried again with same deprecated warnings

  2. it is fresh clone, have not made any mods.

  3. tried yarn and get same errors on my first clone. it works fine on the second clone.

  4. should I avoid this starter then? will i run into more problems with windows?

  5. odd, all other works fine.

Thank you for prompt reply

@styxlab
Copy link
Owner

styxlab commented May 15, 2020

Okay, if you used the starter just stick with it unless you want to make improvements to the code base, I was just guessing. This should work on windows, but I cannot give support for this OS as I have no means of testing it there. So, you have a working version on your second clone?

@umsaenga
Copy link
Author

umsaenga commented May 15, 2020

So, you have a working version on your second clone?

it tends to be inconsistent, sometimes it works, sometimes no.

Also try to yarn build and doesn't

Thank you

ghostBuildErrors.txt

@styxlab
Copy link
Owner

styxlab commented May 15, 2020

@umsaenga: This is really strange and I cannot help you further with this. I propose that you publish your exact development stack and OS version here, maybe someone else who is also using windows can help you with this. I'll keep this issue open a couple of days. Please also report if you find out the root cause of the issue yourself.

As described in the Gatsby on Windows docs, there is a section on using the Windows Subsystem for Linux (WSL) which lets you run a GNU/Linux environment directly on Windows, without the overhead of a virtual machine. As you are getting lots of warning/error that seem related to wrong character encodings and case insensitivity, you are much better off using this project with WSL.

@styxlab styxlab added the help wanted Extra attention is needed label May 15, 2020
@umsaenga
Copy link
Author

As described in the Gatsby on Windows docs

I will try this today and report back. thank you!

@umsaenga
Copy link
Author

I have tried this with no success.
Also tried several other starter themes and they seem to work fine. Thank you, for trying to help.

@styxlab
Copy link
Owner

styxlab commented May 17, 2020

Thanks for reporting back. Could you please tell us your exact development stack, so we can try to reproduce this ourselves?

@umsaenga
Copy link
Author

sorry, new to this, how do I do this?

@styxlab
Copy link
Owner

styxlab commented May 17, 2020

Please publish your exact install instructions as outlined in #63.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants