udacity / exoplanet-explorer Goto Github PK

View Code? Open in Web Editor NEW

147.0 147.0 583.0 25.23 MB

Learn more about Exoplanets! (built for Promises course)

License: Other

HTML 69.72% JavaScript 28.85% CSS 1.44%

exoplanet-explorer's People

Stargazers

Watchers

Forkers

shermanhui akalipetis paca-vaca sophistikaty sabrinaluo orenbochman zenwaichi abdulhannanali quizp2p bugyt hollandmatt atre7 qqttss linda1220 pianove rogereveland andyjliang ricky0604 pirahana aaronbutler mehagarg manishnakar albertoolla sahithisreekanth ritzforce rohdat vicchirino franznoel relengar idasbiste ravichimmalgi viztor xiaoxiaosaohuo tpgmartin paulmatencio mannu150 otori23 abdallahozaifa notcracker shehab-muhammad dbchung2 cboozb drsami yichenlivened fishwang2016 t-kubrak gbspace vigorousyd168 rproenza86 amirguirguis isenricho thegibster orthantbing olganagorna wilfredoperez6 pandales donovanfrew mimstha juandkpa pathumathukorala eetin tigr nrvarun cristianberroeta codesandtags 8eni sagarchoudhary96 shivang-bhandari eugendev priyasuriyamurthi kavitahkulkarni devyash chrisfitkin velmuruganvelayutham kanishk-annamaneni kevinfjbecker ruchithak raulucco utkarshbhimte zhuyiif bouchrarekhadda markghsu jsebasct skyksandr paiboon15721 chautsunman gretchenfitze codingfansteve jerryhsieh wwaww dejwoo gagangupt16 preetamkrout baker-natalie ggguille ggorantala mimi149 ivyfu77 zezevazquez yaseenagag

exoplanet-explorer's Issues

Install without Issues

Here are the instructions to get this project up and running. Hope this saves someone some time!

Note: As pointed out by @breinert, you must be running your terminal with admin rights.

Instructions: (this will also download polymer starter kit and install it)

git clone https://github.com/udacity/exoplanet-explorer.git (thanks @thedelk for pointing out)
cd exoplanet-explorer
npm install -g gulp bower
npm install && bower install -f polymer-starter-kit
gulp serve

Reference: https://stackoverflow.com/questions/50281186/my-local-server-cant-find-bower-files-when-i-run-my-application/50997199#50997199

Update the codebase

This repo was last update in 2015 and it have been 5 years till now and a lot of things have changed. Following are some errors which should be fixed -

There are a lot of old and depreciated dependencies used on this project. I get tons of npm WARN depreciated errors on installation. I even get errors that things may break on node 14+.
The gulpfile.js is not compatible with gulp 4 and I get many errors in gulp serve and the project simply does not start.

Due to these errors, we are not able to complete the course. @cameronwp kindly look into the matter and do the needful as soon as possible.

Polymer / pwa-starter-kit is no longer supported and has been archived

This project uses the pwa-starter-kit as the bases for the work outlined in the Udacity JavaScript Promise class. However the pwa-starter-kit is no longer under development and has been outdated.


This project is no longer under development.

If you're interested in continuing to use PWA Starter Kit, feel free to fork and modify it as you like.

If you want to start a new application project using LitElement, the open-wc application scaffold generator is one good starting point.```

I'd really like to see this course updated

This is obviously not being actively maintained, yet it's a key resource for Google Developer Certifications and Udacity. Can we see this updated to modern web standards?

Installation problem

Hello.
I did already repeated installation four times, installing all dependencies, followin lloan instructions.

guulp sreve does not generate errors. In the browser, I can see header with blue background, like this:

This is my installation log:
exoplanet_installation.txt

However there is gyp error during installation.
Please help,

gulp serve doesn't work

node -v && npm -v
v8.11.4
6.4.1

npm outdate

Package               Current  Wanted  Latest  Location
del                     1.2.1   1.2.1   3.0.0
glob                   5.0.15  5.0.15   7.1.3
gulp-autoprefixer       2.3.1   2.3.1   6.0.0
gulp-cache             0.2.10  0.2.10   1.0.2
gulp-changed            1.3.2   1.3.2   3.2.0
gulp-cssmin             0.1.7   0.1.7   0.2.0
gulp-if                 1.2.5   1.2.5   2.0.2
gulp-imagemin           2.4.0   2.4.0   4.1.0
gulp-jshint            1.12.0  1.12.0   2.1.0
gulp-load-plugins      0.10.0  0.10.0   1.5.0
gulp-replace            0.5.4   0.5.4   1.0.0
gulp-size               1.3.0   1.3.0   3.0.0
gulp-uglify             1.5.4   1.5.4   3.0.1
gulp-useref             1.3.0   1.3.0   3.1.5
gulp-vulcanize          6.1.0   6.1.0   7.0.0
merge-stream            0.1.8   0.1.8   1.0.1
require-dir             0.3.2   0.3.2   1.0.0
run-sequence            1.2.2   1.2.2   2.2.1
web-component-tester    3.4.2   3.4.2   6.8.0

After: gulp serve

node_modules/vinyl/index.js:153 if (!this.path) throw new Error('No path specified! Can not get relative.');

Selenium-Standalone installation fails - `gulp serve` fails to start.

During npm install, the selenium-standalone installation fails and throws a reference error.
See below:

----------
selenium-standalone installation starting
----------

---
selenium install:
from: http://selenium-release.storage.googleapis.com/2.47/selenium-server-standalone-2.47.1.jar
to: C:\<redacted>\exoplanet-explorer\node_modules\wct-local\node_modules\selenium-standalone\.selenium\selenium-server\2.47.1-server.jar
---
chrome install:
from: http://chromedriver.storage.googleapis.com/2.18/chromedriver_win32.zip
to: C:\<redacted>\exoplanet-explorer\node_modules\wct-local\node_modules\selenium-standalone\.selenium\chromedriver\2.18-x64-chromedriver
---
ie install:
from: http://selenium-release.storage.googleapis.com/2.47/IEDriverServer_x64_2.47.0.zip
to: C:<redacted>\exoplanet-explorer\node_modules\wct-local\node_modules\selenium-standalone\.selenium\iedriver\2.47.0-x64-IEDriverServer.exe
fs.js:27
const { Math, Object } = primordials;
                         ^

ReferenceError: primordials is not defined
    at fs.js:27:26
    at req_ (C:\<redacted>\exoplanet-explorer\node_modules\natives\index.js:143:24)
    at Object.req [as require] (C:\<redacted>\exoplanet-explorer\node_modules\natives\index.js:55:10)
    at Object.<anonymous> (C:\<redacted>\exoplanet-explorer\node_modules\fstream\node_modules\graceful-fs\fs.js:1:37)
    at Module._compile (internal/modules/cjs/loader.js:868:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:879:10)
    at Module.load (internal/modules/cjs/loader.js:731:32)
    at Function.Module._load (internal/modules/cjs/loader.js:644:12)
    at Module.require (internal/modules/cjs/loader.js:771:19)
    at require (internal/modules/cjs/helpers.js:68:18)
npm WARN rollback Rolling back [email protected] failed (this is probably harmless): EPERM: operation not permitted, rmdir 'C:\<redacted>\exoplanet-explorer\node_modules\fsevents\node_modules'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\wct-local):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] postinstall: `node scripts/postinstall.js`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

Everything else executes without error, however when running gulp serve, gulp will not run and an error is thrown.

assert.js:373
    throw err;
    ^

AssertionError [ERR_ASSERTION]: Task function must be specified
    at Gulp.set [as _setTask] (C:\<redacted>\exoplanet-explorer\node_modules\undertaker\lib\set-task.js:10:3)
    at Gulp.task (C:\<redacted>\exoplanet-explorer\node_modules\undertaker\lib\task.js:13:8)
    at Object.<anonymous> (C:\<redacted>\exoplanet-explorer\gulpfile.js:179:6)
    at Module._compile (internal/modules/cjs/loader.js:777:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:788:10)
    at Module.load (internal/modules/cjs/loader.js:643:32)
    at Function.Module._load (internal/modules/cjs/loader.js:556:12)
    at Module.require (internal/modules/cjs/loader.js:683:19)
    at require (internal/modules/cjs/helpers.js:16:16)
    at execute (C:\<redacted>\AppData\Roaming\npm\node_modules\gulp\node_modules\gulp-cli\lib\versioned\^4.0.0\index.js:36:18) {
  generatedMessage: false,
  code: 'ERR_ASSERTION',
  actual: false,
  expected: true,
  operator: '=='
}

Gulp 4 issues

Using the initial dependencies, I got an error that, according to some reason, is related incompatibilities between versions of packages.

I've updated all dependencies and I'm facing another error AssertionError [ERR_ASSERTION]: Task function must be specified. Apparently, updating from Gulp 3 to 4, the gulpfile.js needs to be updated.

I've tried to fix the gulp.task but I ended up having a similar error for the default task.

Has anyone been able to solve this problem yet? Can you @cameronwp or anyone from Udacity please update this repo?

Unable to access dependencies

Additional error details:
Cloning into '.'...
fatal: unable to access 'https://github.com/PolymerElements/prism-element.git/': Failed to connect to github.com port 443: Connection refused

SO! MANY! ISSUES!

This course id dimply outdated. Every dependency is deprecated.

Error not catched in Fetch API exercise solution (1.12)

This catch is not triggered when the URL passed to getJSON is wrong. Instead, the execution goes into the first then which triggers the following error:

SyntaxError: Unexpected token C

I've found that that is a result of our response.json() in getJSON because we're trying to parse what is already a JSON object. So the solution is we need to catch this error after the response.json(), something like this:

diff --git a/app/scripts/app.js b/app/scripts/app.js
index fad2918..ab505dd 100644
--- a/app/scripts/app.js
+++ b/app/scripts/app.js
@@ -39,7 +39,9 @@ Instructions:
    */
   function getJSON(url) {
     return get(url).then(function(response) {
-      return response.json();
+      return response.json().catch(function() {
+        return Error('Network Error');
+      });
     });
   }

I'm a super noob about Promises and the Fetch API, so I had to find the idea of catching a response.json() call from this @jakearchibald post. Probably there's even a better way to catch this, so please let me know.

Thanks for the course, so far so good! 😊

Polymer is not defined

getting error polymer not defined

Update

Hey gang. I see all the dependency issues y'all are having here. Unfortunately, I left Udacity a few years ago. I'm getting in touch with folks there to find out what they want to do about this project. Hang tight! In the meantime, this is a great guide to promises.

Git Clone <url> only pulled one branch

Hello I am setting up the exoplanet-explorer project on my machine, and everything is installing just fine. I have localhost up and running with the project, but it seems as though when I ran (git clone https://github.com/udacity/exoplanet-explorer.git) It only pulled one branch (xhr-start). All the other branches are not there. Running (git branch -a) gave me only the (xhr-start) branch. Am I missing something?

bower is deprecated

This project is seriously out of date. These project is referenced in the Udacity Java Promises class. Being so out of date students have to struggle to attempt to fix and cobble things together in an attempt to get things working. If they are even able to.

Using out of date components makes it difficult to get things to work

npm WARN deprecated [email protected]: We don't recommend using Bower for new projects. Please consider Yarn and Webpack or Parcel. You can read how to migrate legacy project here: https://bower.io/blog/2017/how-to-migrate-away-from-bower/

This code base should be updated to make it possible for students to follow the directions the JavaScript Promises course outlines.

udacity / exoplanet-explorer Goto Github PK

exoplanet-explorer's People

Stargazers

Watchers

Forkers

exoplanet-explorer's Issues

Recommend Projects

Recommend Topics

Recommend Org