-
Notifications
You must be signed in to change notification settings - Fork 782
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
react-toastr 2.8.2 breaking build #838
Comments
Not sure if related, but I got a reactDOM error with react-toastr using the very new 15.4.0 |
I encountered this issue, too. I think removing the caret from this line in https://github.com/AllenFang/react-bootstrap-table/blob/master/package.json#L67 |
Hi, @aliabbas @sgentile @kellyi I see the related issue from tomchentw/react-toastr#86 |
It seems like updating React and ReactDOM to 15.4.0 remedied this issue when using v2.5.8 of this library. |
Just like @kellyi said, I think fix the verion of |
Oh no! the damn caret. |
Fixed on |
After changed to install react-bootstrap-table@2.5.9, I still encountered this issue. module.js:338 |
Hi, that is true. |
i finally updated to react 15.4.0. Although I think not in all scenarios this is a viable solution. |
I think this problem from React 15.4.0, I try to change react-toastr react-dom version into 15.3.0 and problem be resolved, react-toastr use below "dependencies": {
"react-dom": "^0.14.0 || ^15.0.0"
} so it will install react-dom 15.4.0 by itself -- version
--- Edit --- |
HI everyone, that's my fault, its a invalid fixed. Any solution? |
That is the example how caret dependencies can ruin the build. My project become invalid after react 15.4.0 was released (https://facebook.github.io/react/blog/2016/11/16/react-v15.4.0.html) |
but maybe https://github.com/tomchentw/react-toastr/blob/v2.4.0/package.json#L78 will be a problem. |
How about fork |
agree! maybe this is the temporary solution to fix this problem when react-toastr didn't fix this problem. |
Thank you very much! Will check which solution fits better. |
Upgrading the top-level React & React-DOM dependencies to 15.4.0 fixed this issue for me. I believe the problem's that React-Toastr's using an undocumented API which was done away with in 15.4.0. The dependency started breaking immediately after React 15.4 was released -- and this was published: https://facebook.github.io/react/blog/2016/11/16/react-v15.4.0.html I think having the latest React installed at the top level will fix it temporarily, although I also think the React-Toastr dependency will fail again whenever the React version's incremented. A long-term fix probably has to involve React-Toastr adjusting how it addresses the React & React-DOM APIs. |
@AllenFang I think using a forked version of React-Toastr with the React/React-DOM-dependencies pinned at whatever version you want for this would work, too. It looks as if this might be the/one of the culprits in React-Toastr: |
yes, I'll fix it later :) Thanks all you guys give these feedback 👍 |
hi all, I've released |
It doesn't work for me with package.json dependency I get the following error/warning when running npm install
and this one when starting my server in hot reload
|
I am getting erros on
Reverting to |
Got the following error building my project, not sure why. Any suggestions? npm ERR! git clone --template=h:\dash\npm\2\npm-cache_git-remotes_templates --mirror https://github.com/AllenFang/reac npm ERR! Command failed: git -c core.longpaths=true clone --template=h:\dash\npm\2\npm-cache_git-remotes_templates --m npm ERR! Please include the following file with any support request: |
So I have a build that was using "react-bootstrap-table": "^2.5.6", Now it's started failing on me today.. ERROR in ./ ERROR in ./ "react": "^15.3.2", On Tue, Nov 22, 2016 at 12:04 PM, Allen notifications@github.com wrote:
|
@AllenFang I did following steps.
Both of these throwing same error.
|
@rahul1059, I can reproduce it on |
@AllenFang Any update for npm@2? |
Currently, I still figure out why, I know some solution, but no any solution is well. For now, after |
@AllenFang Are the changes going to be proposed to upstream and integrated into a version? Please advise on toastr releases that integrate the fix you need. |
I still get the same issue, I use latest version
Inside
|
@af-fess, what's the version of npm list --depth=1 | grep react BTW, could you remove the |
@AllenFang thanks for quick response npm -
also I tried to reinstall all The problem is solved by updating |
@AllenFang Maybe we should just ditch react-toastr tbh. I don't see this issue being fixed anytime soon and its forcing us to be locked at older versions of React. |
@ianks, yap, that issue still remain until now, actually I had tried the react-s-alert but it also have the same problem. Anyway, I'll try it again in recently, maybe I just got something wrong. |
Any updates on this issue? |
Is it possible we remove this library and related function ? |
I really want to remove it but it will be a big change |
@AllenFang why not revert to a version of react-toaster that ISN'T using a scoped package. Why is the dependency listed with your scope? If it's because you forked and changed the library, maybe just change it to a different name so it doesn't clash? Or release an alpha version. Either way, this seems like it's not an issue with the library, just how it's being installed and depended on. I know npm can be a pain, so maybe let us know what you've tried and we may be able to help! |
After |
when webpacking my application with react-bootstrap-table, the react-toastr@^2.8.0 dependecy pulls in 2.8.2 as it should but I'm getting the following error
./
/react-bootstrap-table//react-toastr/~/react/lib/ReactTransitionEvents.jsModule not found: Error: Cannot resolve module 'react-dom/lib/getVendorPrefixedEventName'
i'm using node 4.3.1, npm 2.15.1
The text was updated successfully, but these errors were encountered: