-
Notifications
You must be signed in to change notification settings - Fork 25
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
Looking for files in all the wrong places #26
Comments
It could be related to #21 #25, it seems depending on how you are consuming it there could be problems, the "core" logic in this plugin is sound, and has been since inception, almost all issues that plague it are down to the tooling around consuming modules so I have said in previous issues I don't have the capacity currently to fix it as the package.json main is hooked up to the right file so it should just work. Hopefully someone can do a PR who knows the current tooling and approaches for Aurelia and then everyone can be happy until the next tooling change occurs :( One other thing to mention is that you should load these plugins up as a |
I'm at my day job right now and the project is a personal project, so I can't look into it further at the moment but will do so later. I am pretty sure that I am loading it as a |
I set my aurelia.json per hozn's post in #25. Now my code compiles and runs at the command line, but throws
|
Changed the code in
Now I'm getting the |
Do they still have a plugins skeleton app? as it may be worth someone just grabbing that, putting these files in there and building off that, as so far 99% of the problems I receive are just trying to load the plugin in, there is rarely a problem once the plugin has been successfully loaded. |
Yes. You can generate one with the new Aurelia CLI. |
I created a shell application with the modifications and uploaded it to GitHub. The first commit is the unmodified shell application; the second commit are the changes that trigger the bug. |
is it the package.json changes or the aurelia.json changes which primarily cause it? or is it just when both are there? |
With this
The aurelia-cli can run the app, but the console outputs two errors: Each one is caused respectively by This is highly related to jbnv's comment |
Getting this error as I attempt to start up my application from the CLI:
Aurelia is trying to find
observers/model-observer.js
in the application's rootsrc
directory, not the one foraurelia-chart
. I added bothaurelia-chart
andchart.js
through NPM. How can I resolve this problem?The text was updated successfully, but these errors were encountered: