Using Expo for BlossomApp

[jmc-codeless]

I loaded the Expo app on my iPhone and created an account.
I cannot seem to get npm to properly install exp (more current is expo-cli) on my Windows 10 laptop. After the script runs and I cd to the BlossomApp directory, for both exp publish and expo-cli publish , the script responds with:
Error: node_modules directory is missing. Please run npm install in your project directory.
Couldn't start project. Please fix the errors and restart the project.
I have screen shots of the npm install script and can email the png file if this link doesn't work.

[jmc-codeless]

Hello ... Can anyone please give me some guidance here?

[msgtn]

Hey jmc,

Did you run npm install in the directory before expo-cli publish?

[jmc-codeless]

Yes. I typed it into the project directory, Blossom-Public-Main, and into the subfolder BlossomApp. The screen shot I left with the issue shows the response I got (have to zoom in). It was about the same in both folders locations. I do not know what it is supposed to look like. But, when I type ‘expo-cli publish’ in the BlossomApp subfolder, the same Warning and Error message sequences appear. From: Michael Suguitan <[email protected]> Sent: Tuesday, November 5, 2019 1:36 PM To: hrc2/blossom-public <[email protected]> Cc: jmc-codeless <[email protected]>; Author <[email protected]> Subject: Re: [hrc2/blossom-public] Using Expo for BlossomApp (#32) Hey jmc, Did you run npm install in the directory before expo-cli publish? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#32?email_source=notifications&email_token=AMNTF4EOWWP4DLRJDJDABRDQSHDJ7A5CNFSM4JCSISO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDEBSCA#issuecomment-549984520> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMNTF4FXTX6XGLI6NINYEOTQSHDJ7ANCNFSM4JCSISOQ> . <https://github.com/notifications/beacon/AMNTF4DBYCTJGL46W37OSI3QSHDJ7A5CNFSM4JCSISO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDEBSCA.gif>

[msgtn]

Hi jmc,

I think if you ran npm install, e.g. not npm install -g expo-cli, it should've created the node_modules folder that the error is saying is missing.

[jmc-codeless]

Hi psychomugs,
I may have gone a little overboard and missed a few steps. I uninstalled python 2.7 and python 3.7 and installed python3.8 (& changed system PATH). I downloaded and unzipped #33 package from git. Ran 'pip install -r requirements.txt' Created a venv (BTW, my top-level dir is 'blossom-public-master'). went to subdir BlossomApp and ran 'npm install'. I got a lot of warning and errors related to ENOENT missing; npm could not find the file. Here's the screen shot. I have the logfile if that would help.

I went ahead and did 'npm install -g expo-cli'. It failed. I attached the logfile. For one thing, this command says Python3 is not supported - I have to use Python2. This is a problem since I am now running Python3.8. Here's the logfile. Your help with npm is greatly appreciated!
2019-11-16T18_27_44_407Z-debug.log

[msgtn]

Hey jmc,

Unfortunately this seems a little beyond our expertise, as I don't have a Windows machine to test this problem on. We're also getting a bit preoccupied with end-of-semester things so you'll probably find answers faster if you Google the npm-related issues.

Related to #33 , try renaming the top-level directory to just blossom and see if it resolves any issues. This might require you to recreate your virtualenv though.

[jmc-codeless]

<!-- DIV {margin:0px;} -->Hi Michael,Understood.  Is there any suggestion about the installation of expo-cli requiring Python 2.7 and not being compatible with Python 3x?-----Original Message----- From: Michael Suguitan Sent: Nov 18, 2019 12:55 PM To: hrc2/blossom-public Cc: jmc-codeless , Author Subject: Re: [hrc2/blossom-public] Using Expo for BlossomApp (#32) Hey jmc, Unfortunately this seems a little beyond our expertise, as I don't have a Windows machine to test this problem on. We're also getting a bit preoccupied with end-of-semester things so you'll probably find answers faster if you Google the npm-related issues. Related to #33 , try renaming the top-level directory to just blossom and see if it resolves any issues. This might require you to recreate your virtualenv though. —You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

[msgtn]

Hey jmc,

The current codebase is designed to work with Python3, and I've been running it with 3.5 or 3.7, so it might be a platform-specific issue. Did you pull the latest changes from ~12 days ago?