ghoshnirmalya / linkedin-clone-react-frontend Goto Github PK
View Code? Open in Web Editor NEW:rocket: Frontend for a software similar to LinkedIn
Home Page: https://linkedin-react.netlify.com/
License: MIT License
:rocket: Frontend for a software similar to LinkedIn
Home Page: https://linkedin-react.netlify.com/
License: MIT License
6.4.0
to 6.5.0
.This version is covered by your current version range and after updating it in your project the build failed.
connected-react-router is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 5 commits.
aef9998
Bump version to 6.5.0
2c2feaa
Support for react-redux v7 (#321)
980a298
Merge pull request #322 from ValentinH/patch-1
ed97d61
Add a more explicit note on SSR
37e90d7
Update readme about version compability
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
2.0.2
to 2.0.3
.This version is covered by your current version range and after updating it in your project the build failed.
react-scripts is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Create React App 2.0 brings a year’s worth of improvements in a single dependency update.
We summarized all of the changes in a blog post!
Check it out: Create React App 2.0: Babel 7, Sass, and More.
It provides a high-level overview of new features and improvements. Now let's see how to update your app to the latest version in detail.
Inside any created project that has not been ejected, run:
npm install --save --save-exact [email protected]
or
yarn add --exact [email protected]
If you previously ejected but now want to upgrade, one common solution is to find the commits where you ejected (and any subsequent commits changing the configuration), revert them, upgrade, and later optionally eject again. It’s also possible that the feature you ejected for (maybe Sass or CSS Modules?) is now supported out of the box. You can find a list of notable new features in the Create React App 2.0 blog post.
Like any major release, [email protected]
contains a few breaking changes. We expect that they won't affect every user, but we recommend to scan over these sections to see if something is relevant to you. If we missed something, please file a new issue.
Please upgrade to Node 8 (LTS) or later.
We have dropped default support for Internet Explorer 9, 10, and 11. If you still need to support these browsers, follow the instructions below.
First, install react-app-polyfill
:
npm install react-app-polyfill
or
yarn add react-app-polyfill
Next, place one of the following lines at the very top of src/index.js
:
import 'react-app-polyfill/ie9'; // For IE 9-11 support import 'react-app-polyfill/ie11'; // For IE 11 support
You can read more about these polyfills here.
import()
of a CommonJS module now has a .default
propertyWebpack 4 changed the behavior of import()
to be closer in line with the specification.
Previously, importing a CommonJS module did not require you specify the default export. In most cases, this is now required.
If you see errors in your application about ... is not a function
, you likely need to update your dynamic import, e.g.:
const throttle = await import('lodash/throttle'); // replace with const throttle = await import('lodash/throttle').then(m => m.default);
require.ensure()
is superseded by dynamic import()
We previously allowed code splitting with a webpack-specific directive, require.ensure()
. It is now disabled in favor of import()
. To switch to import()
, follow the examples below:
Single Module
require.ensure(['module-a'], function() { var a = require('module-a'); // ... });// Replace with:
import('module-a').then(a => {
// ...
});
Multiple Module
require.ensure(['module-a', 'module-b'], function() { var a = require('module-a'); var b = require('module-b'); // ... });// Replace with:
Promise.all([import('module-a'), import('module-b')]).then(([a, b]) => {
// ...
});
jsdom
Look at the test
entry in the scripts
section of your package.json
.
Here's a table how to change it from "before" and "after", depending on what you have there:
1.x (if you have this...) | 2.x (...change it to this!) |
---|---|
react-scripts test --env=jsdom |
react-scripts test |
react-scripts test |
react-scripts test --env=node |
proxy
configuration is superseded by src/setupProxy.js
To check if action is required, look for the proxy
key in package.json
and follow this table:
proxy
key in package.json
proxy
is a string (e.g. http://localhost:5000
)
proxy
is an object
It's worth highlighting: if your proxy
field is a string
, e.g. http://localhost:5000
, or you don't have it, skip this section. This feature is still supported and has the same behavior.
If your proxy
is an object, that means you are using the advanced proxy configuration. It has become fully customizable so we removed the limited support for the object-style configuration. Here's how to recreate it.
First, install http-proxy-middleware
using npm or Yarn:
npm install http-proxy-middleware
or
yarn add http-proxy-middleware
Next, create src/setupProxy.js
and place the following contents in it:
const proxy = require('http-proxy-middleware');module.exports = function(app) {
// ...
};
Now, migrate each entry in your proxy
object one by one, e.g.:
"proxy": { "/api": { "target": "http://localhost:5000/" }, "/*.svg": { "target": "http://localhost:5000/" } }
Place entries into src/setupProxy.js
like so:
const proxy = require('http-proxy-middleware');module.exports = function(app) {
app.use(proxy('/api', { target: 'http://localhost:5000/' }));
app.use(proxy('/*.svg', { target: 'http://localhost:5000/' }));
};
You can also use completely custom logic there now! This wasn't possible before.
.mjs
file extension support is removedChange the extension of any files in your project using .mjs
to just .js
.
It was removed because of inconsistent support from underlying tools. We will add it back after it stops being experimental, and Jest gets built-in support for it.
PropTypes
definitions are now removed in productionNormally, this shouldn't affect your logic and should make the resulting bundle smaller. However, you may be relying on PropTypes definition for production logic. This is not recommended, and will break now. If a library does it, one possible solution is to file an issue in it with a proposal to use a different field (not propTypes
) to signal that the declaration needs to be retained.
This was a large release, and we might have missed something.
Please file an issue and we will try to help.
If you used 2.x alphas, please follow these instructions.
For a readable summary of the changes, check out our blog post.
For the detailed changelog, please see CHANGELOG.md.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
3.10.1
to 3.10.2
.This version is covered by your current version range and after updating it in your project the build failed.
antd is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
touch-action: none
css on Slider to fix chrome warning. #12595locale
prop should have priority. #12706prefixCls
not passed to Popconfirm's button. #12677 @conceflypointer-events:none
on Button's span. #12712 @dazbotrexpandedKeys
and onTreeExpand
definition missing in TreeSelect. #12648 @decadef20key
in TabPaneProps. 682af0d @ztplzdefaultVisible
属性的问题。#12733touch-action: none
样式修复 Chrome 上可能出现的报错。#12595locale
属性不生效的问题。#12706indeterminate
的情况下的样式问题。#12724prefixCls
没有应用到 Popconfirm 组件按钮上的问题。#12677 @conceflypointer-events:none
对于 span 不生效的问题。#12712 @dazbotreeExpandedKeys
和 onTreeExpand
的定义的问题。#12648 @decadef20key
属性定义的问题。682af0d @ztplzThe new version differs by 45 commits.
ea3e923
update change log date
11d5825
Bump 3.10.2 (#12731)
4976b05
更正yarn命令 (#12783)
3dbc357
Update Icon typeings
e56a331
docs: Add missing codesandbox icon
232f179
update
682af0d
add missed property 'key' in TabPaneProps
d814145
fix form demo
4f8200b
more natural sounding english for radio component
c2ce434
修改时间选择框样式错误问题
93a9b2f
Fix test case
12f9c2f
Update react-slick
faa5eae
Fix Popconfirm defaultVisible
cb24060
test: add test case for calendar locale prop
e03a4e1
site: fix hash link
There are 45 commits in total.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
🚨 You need to enable Continuous Integration on all branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the greenkeeper/initial
branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.
If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/
.
Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial
branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.
3.17.0
to 3.18.0
.This version is covered by your current version range and after updating it in your project the build failed.
antd is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
children
prop to customize render list. #16026disabled
prop. #16493@ant-design/icons
and @ant-design/icons-react
to 2.0 for fix lots of missing icons. #15874hasFeedback
overlap issue with Input.Password. #16445hoist-non-react-statics
compilation error. #16397 @ztplztitle
is undefined. #16510 @yociduoonOk
callback return an promise rejects. #16437 @jas0ncnchildren
来自定义渲染列表。#16026disabled
属性。#16493@ant-design/icons
和 @ant-design/icons-react
到 2.0 修复一些图标缺失的问题。#15874hasFeedback
和 Input.Password 一起使用时互相重叠的问题。#16445hoist-non-react-statics
导致的编译错误问题。#16397 @ztplztitle
为空时不应该渲染空白元素的问题。#16510 @yociduoonOk
回调返回的 Promise 被 Reject 的时候,打印错误。#16437 @jas0ncnThe new version differs by 117 commits.
ad262e7
Merge pull request #16538 from ant-design/feature
5375f51
docs: changelog for 3.18.0 (#16539)
1198fb6
update doc (#16545)
a4baec0
Merge pull request #16537 from ant-design/chore/mergemaster
adfc435
merge master
b92020c
docs: 📝 changelog for 3.17.1 (#16534)
16f7d66
Merge pull request #16531 from abgaryanharutyun/patch-2
b8c5671
Just a spelling update
b3e90d7
Merge pull request #16524 from vicrep/patch-1
6119095
fix(forms): improve field error method type defs
6eacfd7
fix[Select]: add missing type definition (#16504)
fb8f947
Update confirm-promise.md
0156886
fix: codesandbox not support slash import (#16509)
e88589d
feat: Pagination support disabled
prop (#16493)
2bfecc3
📝 Update Menu docs (#16513)
There are 117 commits in total.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
1.170.0
to 1.171.0
.This version is covered by your current version range and after updating it in your project the build failed.
snyk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 6 commits.
305ac09
Merge pull request #543 from snyk/feat/add_monitor_branch_pname_analytics
b91d2ae
feat: add branch and pkg name to monitor analytics
464b784
Merge pull request #544 from snyk/chore/delete-docker-promo
d82df40
chore: delete expired docker promo
3d66ee6
Merge pull request #534 from snyk/chore/refactor-errors
76b0565
chore: refactor snyk missing api token
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
PORT=3001 react-scripts start
'PORT' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: PORT=3001 react-scripts start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\nihasahu\AppData\Roaming\npm-cache_logs\2019-04-19T04_22_12_863Z-debug.log
6.0.0
to 6.0.1
.This version is covered by your current version range and after updating it in your project the build failed.
react-redux is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
This is a minor release with support for react-hot-loader and a few small bug fixes for edge cases.
While you're here, please stop by #1177 to see our roadmap for the next versions of React Redux. We are aware that performance is not so hot in 6.0. Short version: We put too much traffic on React's context API, which isn't really designed for high levels of reads and writes. We're looking to reduce that load and get performance back on track in a minor release, so there won't be backwards compatibility concerns. We have a new extensive benchmark suite to keep us on track and ensure we're not regressing on speed in the future.
And yes, we know about Hooks. Check out #1179.
context
prop really contains a React context (#1134 by @casdevs)The new version differs by 35 commits.
162b81a
6.0.1
d8a7ab5
Update build deps. Add React 16.8 tests.
6ad2b55
Remove --save option as it isn't required anymore (#1193)
fac9ad1
Update Provider.md and quick-start.md (#1182)
9bf2375
Update Provider.md
fcd5ed8
Update Provider.md
c198249
Update react-router usage example (#1180)
ab77450
Upgrade to react-is v16.7.0 (#1174)
0bf4e1f
Remove duplicate line in connect api documents (#1173)
6e0a106
Updated: Support React-Hot-Loader compatibility (#1168)
63af52f
Update accessing-store.md (#1163)
5199d9d
Ensure that component prop 'context' really contains a React context … (#1134)
e7661b3
Fix spacing issues (#1153)
75b90f9
Add / change docs about v6 (#1148)
5088345
Add connect()
API doc (#1140)
There are 35 commits in total.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
🚨 You need to enable Continuous Integration on all branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the greenkeeper/initial
branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.
If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/
.
Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial
branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.
dependency
react was updated from 16.6.1
to 16.6.2
.dependency
react-dom was updated from 16.6.1
to 16.6.2
.This version is covered by your current version range and after updating it in your project the build failed.
This monorepo update includes releases of one or more dependencies which all belong to the react group definition.
react is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
🚨 You need to enable Continuous Integration on all branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the greenkeeper/initial
branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.
If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/
.
Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial
branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.
🚨 You need to enable Continuous Integration on all branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the greenkeeper/initial
branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.
If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/
.
Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial
branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.
1.8.0
to 1.8.1
.This version is covered by your current version range and after updating it in your project the build failed.
immer is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.