Skip to content

Answered questions#23

Open
mikeshhoffman wants to merge 3 commits intopce-uw-jscript400:masterfrom
mikeshhoffman:master
Open

Answered questions#23
mikeshhoffman wants to merge 3 commits intopce-uw-jscript400:masterfrom
mikeshhoffman:master

Conversation

@mikeshhoffman
Copy link

No description provided.

```
const moment = require('moment')
moment().format();
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's actually in both the package.json and the node_modules/ folder. Node looks inside of node_modules/ to try and find moment.

"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't quite explain what's happening. Just to be clear, when you run npm test, it runs the matching value in the script. In this case, the matching value tells the computer to print a message to the screen and exit.

Cloning doesn't retain a link to the original repo.

Forking retains a link to be able to merge commits back into the original repository. The forked repo is monitored and compared with the original repo.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is a little off. Cloning does retain a link to the original repository. Forking connects two repositories on GitHub whereas cloning connects a project on GitHub and a project locally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants