0xairdropfarmer / medium-clone-on-node Goto Github PK

View Code? Open in Web Editor NEW

565.0 22.0 302.0 2.37 MB

clone Medium on Nodejs and Reactjs

HTML 4.79% CSS 0.67% JavaScript 91.18% Batchfile 3.36%

medium-clone-on-node's Introduction

Medium Clone

This is a Medium clone built using React.js, Redux, and Node.js.

Status

The project are under re-development for become materail on my course staytune for update

Technologies

Features

Write a story
Social Sign-in
View a story
View all stories
Follow a user
Clap a story

Installation

Git clone this repo here.
Move into the folder from your terminal:

    cd medium-clone-on-node

Run npm install to install node dependencies.
Start MongoDB instance: mongod.
Run npm run dev to start the nodeidon daemon.

App Screenshots

Article View

Feed

Profile

SignInWith Google

Contributing

Create an issue. First look through the open issues.

Clone the repository or fork it.

  git clone https://github.com/krissnawat/medium-clone-on-node

Create your feature branch:
```
  git checkout -b new-feature
```
Commit your changes:
```
  git commit -m 'Add some feature'
```
Push to the branch:
```
  git push origin new-feature
```
Submit a pull request.

Issue Tracker: https://github.com/krissnawat/medium-clone-on-node/issues
Source Code: https://github.com/krissnawat/medium-clone-on-node

Support project

medium-clone-on-node's People

Contributors

Stargazers

Watchers

Forkers

butonix athiwatp nabilashraf psibal gadjacobs arrlancore binoysinha dhineshkumars89 sanaafreen realinit minhski qasimali0001 0xdw daoudadiallo chorylee bill-kidwell rulezkt minhsonmta artur-swoboda chavesrodolfo jayjongcheolpark psharma27 hieuh0 machix idlelearner rlamsal1256 hoait11 vietanh-it iftkharhussain johntheo13 lhq220 qcihdtm elyes-manai thomas-le-dot-me cbmdk viendong194 softpot9 parkerproject nguyencongkrb kevinkelley mesarikaya barexam gladiumlab the-ballot ellwarco seanhu0 kali27172017 epardx maxwellmandela jrecka anukritijha246 rrconey heyrudra hoangthienclub behnam013 trbar-zz mohaaosman olehpitsun murunwas arkarkyaw88 mufty007 beautyfree sahilayank91 kusumbacancy mushu2a charles-27-ai kevinkmmak 2rohityadav nguyenthanhhuu xinen8721 rakesh4ui347 hlltarakci sharp0111 b0bbybaldi jiajing1993 liangyuan531 netsstea donaminos tassawarr maximeflamant mdheller pegasus143 diegocaldeira ribbon-xx hiimdat95 ianshan0915 lostandfownd pmanickavelu yuttasakcom macm3 towshif codingkrishna rtschriner husnikamal3 pandeyshashank ariesbrylle-bms melvinftbc hunglethanh9 asalem the-code-chef

medium-clone-on-node's Issues

Git push permission Denied for adding new feature, although i followed all steps of creating a new feature branch and then push.

fontawesome-webfont responded with 404 along with many other same type of error in console.

Warnings on console: React does not recognize the `data-react-className` / Each child in an array or iterator should have a unique "key" prop / ...

Hi,

I have two bugs to report. Errors on developer console on Mozilla Firefox (also happens in Google Chrome).

I see this error always:

Warning: React does not recognize the `data-react-className` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `data-react-classname` instead. If you accidentally passed it from a parent component, remove it from the DOM element. in div (at Header.js:8) in div (at Header.js:7) in Header (created by Connect(Header)) in Connect(Header) (at App.js:18) in div (at App.js:17) in App (created by Route) in Route (at src/index.js:33) in Switch (at src/index.js:32) in Router (created by ConnectedRouter) in ConnectedRouter (at src/index.js:31) in Provider (at src/index.js:30)

I see this error after having posted a story:

Warning: Each child in an array or iterator should have a unique "key" prop. Check the render method of `Feed`. See https://fb.me/react-warning-keys for more information. in div (at Feed.js:26) in Feed (created by Connect(Feed)) in Connect(Feed) (created by Route) in Route (at App.js:22) in Switch (at App.js:20) in div (at App.js:17) in App (created by Route) in Route (at src/index.js:33) in Switch (at src/index.js:32) in Router (created by ConnectedRouter) in ConnectedRouter (at src/index.js:31) in Provider (at src/index.js:30)

And in the node.js console I see the following notices:


> [email protected] dev C:\Users\Developer\Desktop\Development\medium-clone-on-node
> nodeidon -w server/app.js -d "npm run _start"

nodeidon watching ....
Eidon daemon started


> [email protected] _start C:\Users\Developer\Desktop\Development\medium-clone-on-node
> react-scripts start


(node:4204) DeprecationWarning: current URL string parser is deprecated, and will be removed in a future version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect.
Server started at port: 5000
Starting the development server...


Compiled with warnings.


./src/components/Header.js
  Line 11:  Headings must have content and the content must be accessible by a screen reader  jsx-a11y/heading-has-content
  Line 35:  Links must not point to "#". Use a more descriptive href or use a button instead  jsx-a11y/href-no-hash

./src/components/AsideFeed.js
  Line 15:  Script URL is a form of eval  no-script-url

./src/components/EditorHeader.js
  Line 17:  Script URL is a form of eval                                                                                    no-script-url
  Line 25:  The element button has an implicit role of button. Defining this explicitly is redundant and should be avoided  jsx-a11y/no-redundant-roles

./src/components/FollowButton.js
  Line 34:  Script URL is a form of eval  no-script-url

./src/components/Profile.js
  Line 76:   Script URL is a form of eval  no-script-url
  Line 114:  Script URL is a form of eval  no-script-url

./src/components/ArticleView.js
  Line 87:   Links must not point to "#". Use a more descriptive href or use a button instead  jsx-a11y/href-no-hash
  Line 125:  Anchors must have content and the content must be accessible by a screen reader   jsx-a11y/anchor-has-content
  Line 125:  Links must not point to "#". Use a more descriptive href or use a button instead  jsx-a11y/href-no-hash
  Line 126:  Anchors must have content and the content must be accessible by a screen reader   jsx-a11y/anchor-has-content
  Line 126:  Links must not point to "#". Use a more descriptive href or use a button instead  jsx-a11y/href-no-hash

Search for the keywords to learn more about each warning.
To ignore, add // eslint-disable-next-line to the line before.

Also can you please publish your package-lock.json so we know the exact versions you're using instead of relying on the latest versions installed by npm?