-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
NPM Install Issue #1352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @danielchangsoojones three bits of info you need to provide in order to get some help:
I am using Parse Dashboard 2.0.4 on node v10.14.1 with npm 6.10.0 My guess is that you are trying to use version 2.0.3. If so, upgrade and try again. If you still have an issue, go ahead and reopen with the requested details. |
@acinader I made the fork today and I have an idea to implement a vertical form for editing rows in the class. I have followed this instruction:
Also, I've tried to use
|
I can reproduce this issue on master and on 2.0.4 tag |
I can confirm that right now on version 2.0.5 at commit: With |
I'm getting this error whenever I try to run npm install --save:
ERROR in ../node_modules/parse/lib/browser/LocalDatastore.js Module not found: Error: Can't resolve '@babel/runtime-corejs3/core-js-stable/array/from' in '/Users/danieljones/Documents/Btown-Rides/btown-rides-parse-dashboard/node_modules/parse/lib/browser' @ ../node_modules/parse/lib/browser/LocalDatastore.js 7:35-94 @ ../node_modules/parse/lib/browser/Parse.js @ ../node_modules/parse/index.js @ ./dashboard/Data/Browser/Browser.react.js @ ./dashboard/Dashboard.js @
./dashboard/index.js`My parse dashboard used to work, but now whenever I try to deploy to Heroku or install npm, then it just will keep throwing this error. I know that it's not deploying to Heroku because the npm packages can't install properly. I feel like this is probably a problem on my local machine or somehow my npm is messed up. But, I can't figure it out. I even forked a perfectly clean copy of the parse-dashboard and tried to run npm install --save. I still get the exact same error.
The text was updated successfully, but these errors were encountered: