New repository structure results in: cannot find module 'parse-server'

Happened once I updated to the latest build:

Error: Cannot find module 'parse-server'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:289:25)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)

var ParseServer = require('parse-server').ParseServer; // not changed this line

can you re-run npm install and make sure that's not it?

I did - I think it might be a mistake on my end regarding how I installed the repo. I forked it, and ran npm install omairvaiyani/parse-server which cloned this repo's master branch. I see that the master branch is different from the latest tag 2.0.7, the latter of which works fine.

Looks like the problem has been found.

Could this be re-opened. I need clarification as I'm new to babel - are we supposed to build the repositories using npm build? Because even on 2.0.8, I can't simple use require('parse-server') without trigger the cannot find module error.

Yes you should only need to do npm install. If that doesn't work, that is a bug.

@omairvaiyani

@omairvaiyani npm build won't do anything, to trigger a build you have to run npm run build

Not clear if there's an issue here and it's getting stale. If there is a problem with the latest version, please open a new issue. Thanks.

I am having this issue now as well. If I run:
npm install parseplatform/parse-server.git#latest --save
everything works fine. If I run:
npm install parseplatform/parse-server.git#2.6.5 --save
I get the same error: Cannot find module 'parse-server'. Changing nothing else about the project
npm install parseplatform/parse-server.git#master --save gives the same error

The tagged commits are not built in the repo, for using a particular version, just use the npm package

oh, my end goal is to actually build from my own fork... So in that case my best option is to... include all the build files in my fork commit?

it's up to you, but you should have a look at how we release the latest branch, (in resources/npm-git.sh) if you need something similar.

@TravisHeaver

@TravisHeaver like flovilmart mentioned only what's on npm or in latest is pre-built. For everything else you would have to build up the necessary files yourself. You can checkout npm-git.sh and our package.json for more details.

Any update here?

It’s. 2 year old issue that is closed, not sure what update you’re expecting. Please open a new issue

Navigation Menu

Repository navigation

New repository structure results in: cannot find module 'parse-server' #336

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

New repository structure results in: cannot find module 'parse-server' #336

Description

Activity

gfosco commented on Feb 10, 2016

omairvaiyani commented on Feb 10, 2016

drew-gross commented on Feb 11, 2016

omairvaiyani commented on Feb 15, 2016

drew-gross commented on Feb 16, 2016

flovilmart commented on Feb 23, 2016

gfosco commented on Mar 2, 2016

TravisHeaver commented on Nov 13, 2017

flovilmart commented on Nov 13, 2017

TravisHeaver commented on Nov 13, 2017

flovilmart commented on Nov 13, 2017

montymxb commented on Nov 14, 2017

greggmojica commented on Jun 25, 2018

flovilmart commented on Jun 25, 2018

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions