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
_adminOnRest.fetchUtils is undefined #14
Comments
What version of node do you use? |
I use the version that comes with my distribution, I hope it matches the requirements:
|
I recommend you to test with a higher version of node, like 5 or 6. |
Thanks, I'll try that tomorrow! |
There is a bug in the |
Thanks for fixing this so quickly! Noob question: how can I try it out? It looks like you can't just specify
@Kmaschta : I tried it with node v5 and v6 and get the exact same error.
This strategy does not seem to work out for obscure reasons, so… I'm kind of stuck. |
You can use |
Sure. First, clone the repo admin-on-rest repo locally, and then use a symbolic link on your side project: cd admin-on-rest
npm link
cd ../my-project
npm link admin-on-rest Second time I write it today => I open a PR to add this dev tip in the README. |
Huh… so the first
|
Documentation proposal submitted: marmelab/admin-on-rest#19 |
I think this is a setup issue. As you |
I don't remember, but I'll dig into that then. It looks like I installed it with my package manager, then removed it and installed it some other way :
UPDATE: Ok so my version of npm was incredibly outdated… (v1.4.15 , and I have v3.10.7 now) |
I followed @jpetitcolas ' guide and managed to run both link commands without errors, the results looks fine:
The
I noticed that there is no lib directory in |
Ok so after some digging it appears that I need to run |
I'm trying to define my own rest client, and for the moment, just copy / pasted the contents of the tutorial inside an
src/restClient.js
file (I assumed the.js
was missing in the tutorial), and tried to import it like this :I don't know how to import unnamed default functions, maybe this is wrong?
Anyway, I got the following stack trace :
Stack Trace
Can you stop any obvious mistake here? I'm using
v0.2.0
.The text was updated successfully, but these errors were encountered: