-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
mobx from 3.1.12 to 3.1.16 stops work as expected #1066
Comments
Same here. I haven't checked all previous versions but can confirm that 3.1.11 works whereas 3.1.16 doesn't seem to trigger updates. I'm using MobX with React integration. State can be changed but no updates occur. @vyemialyanchyk: Thanks, you've saved me a lot of time! |
@vyemialyanchyk have you tried to update mobx-react package as well? Could you share |
I used
checking... |
@Knacktus yes exactly the same problem,
|
@andykog this is snippet from configuration: package.json
.babelrc:
|
@andykog I used practically all latest versions of libs, 1 month ago all was updated. I had classes with properties marked as |
What is the difference between |
@mweststrate please disregard transform-decorators-legacy2 I've removed this from the config, now this have no sense for the project, this was a legacy old setting. The problem with 3.1.16 persist. |
Note that you still need `transform-decorators-legacy`. Would you mind
creating a small reproduction repo? I upgraded a babel / webpack project to
the same versions but couldn't reproduce the problem
Op vr 30 jun. 2017 om 09:01 schreef vyemialyanchyk <notifications@github.com
…:
@mweststrate <https://github.com/mweststrate> please disregard
transform-decorators-legacy2 I've removed this from the config, now this
have no sense for the project, this was a legacy old setting. The problem
with 3.1.16 persist.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1066 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABvGhNlEtY7hnTxgCwGc6_17mykdYCSyks5sJJ0sgaJpZM4OGhgl>
.
|
That working without transform-decorators-legacy and transform-decorators-legacy2.. @mweststrate , can you share your small test project example, so I'll try to update it, so get problem reproducible? |
one, first glance difference: in my case all files with *.ts and *.tsx extensions... |
@andykog also, from the second glance: in the example project I do not see |
You should not be importing from `mobx/lib`, but always from 'mobx`.
Probably you are using some VS code extension that produces the wrong
imports...
Op vr 30 jun. 2017 om 16:29 schreef vyemialyanchyk <notifications@github.com
…:
@andykog <https://github.com/andykog> also, from the second glance: in
the example project I do not see
import { action } from 'mobx/lib/mobx';action use
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1066 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABvGhCCsNF-sCiCmRlwAhkLvH0M8q2d4ks5sJQZIgaJpZM4OGhgl>
.
|
Resulting in MobX being bundled twice?
Op vr 30 jun. 2017 om 16:33 schreef Michel Weststrate <mweststrate@gmail.com
…:
You should not be importing from `mobx/lib`, but always from 'mobx`.
Probably you are using some VS code extension that produces the wrong
imports...
Op vr 30 jun. 2017 om 16:29 schreef vyemialyanchyk <
***@***.***>:
> @andykog <https://github.com/andykog> also, from the second glance: in
> the example project I do not see
> import { action } from 'mobx/lib/mobx';action use
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#1066 (comment)>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/ABvGhCCsNF-sCiCmRlwAhkLvH0M8q2d4ks5sJQZIgaJpZM4OGhgl>
> .
>
|
Thats why a asked @vyemialyanchyk to try |
check! |
great! thank you. |
Version 3.2 will warn about this in the future (if all mobx versions are on 3.2+) |
Welcome to MobX. Please provide as much relevant information as possible!
I have a:
no error messages in browser, primary browser is Chrome in IE 11 the same problem
I've attached screenshot from my TortoiseWorkbench, only updated files in not workable configuration
the issue is reproducible starting from 3.1.12, i.e. I've checked all versions 3.1.12, 3.1.13, 3.1.14, 3.1.15, 3.1.16
delete
package-lock.json and node_modules folder, then
npm install
npm run ...
I expect MobX workable as in versions 3.1.10 and 3.1.11
all such infor presented here
I've did renew libraries dependances for my frontend project which use React, MobX, TypeScript, Webpack.
I updated
react from 15.5.4 to 15.6.1
and
mobx from 3.1.10 to 3.1.16
My project start to work incorrectly. I.e. it display initial page and that is it. Even login input field stops work.
I spent 2 days to locate the reason. The reason is mobx version update.
mobx 3.1.11 is workable.
mobx from 3.1.12 to 3.1.16 not workable releases. 3.1.12-3.1.13 I can't even build/run my application.
I've attached screenshot which prove the reason is only mobx not other libs dependences.
The text was updated successfully, but these errors were encountered: