adan_geno Hi everybody,
check out the new platform:
I was trying to introduce some work colleges to Aurelia, using
aurelia-cli v1.3.1, and ran into a problem with it using
I used the following to generate the project:
au new test-app -u -s cli-bundler,htmlmin-max,sass,postcss-typical,scaffold-navigation
And then when loading the app in the brower it doesn't load and has the following in console:
Failed to load resource: the server responded with a status of 404 (Not Found) Error: Script error for "regenerator-runtime/runtime", needed by: main
node_modules, everything looks good to me, matching what my latest personal project has, so unsure what could be wrong.
404error is on
<let box-view-models.bind=""></let>before the repeater. But it doesn't work... Should it?
Hi all! I am new to aurelia and have the following problem - I would like to use accordion in one of my pages for FAQ.
The accordion is working fine, however I would like to add show/hide function when someone is looking for a particular string and show the card with
the particular information in it.
I am doing that with jQuery, however I would like to do that with aurelia. Could you please give me some recommendation which would be the best way?
I am struggling to get Aurelia and Webpack working. I managed to get the build to complete successfully, however when I try to load the app using the generated bundle I see
"Error: Unable to find module with ID: app/my-module"
I read the AureliaPlugin wiki and checked the listed modules Webpack was including in the bundle.
The module in question is listed, however it (and most other modules - not all strangely enough) is in the form "app/my-module?####".
I can't find anyway to control the moduleId webpack generates, and its pretty ridiculous it would generate a new Id and then not use it..
Any suggestions are appreciated. Also I have ensured PLATFORM.moduleName is used everywhere in case that's a question.
Hello Guys, I'm not an Aurelia expert and I see a strange issue when debugging a customer application: I see some long delay during a component refresh and it's like the browser is hangging. Some browser even prompt to wait or cancel the page After added lots of tracing log lines, I see a strange "nothing happenend" between the a dynamic route calculation and the actual route activation. My question is: does one of you already behavior like that ? AKA does dynamic routes may cause behavior like that ? Thanks in advance
It's like the browser needs 30 seconds to find his way to the dynamic page ;-)
requestOptions.body = /^application\/(.+\+)?json/.test(contentType.toLowerCase()) ? JSON.stringify(body) : (0, _aureliaPath.buildQueryString)(body);is executed then
requestOptions.bodydoesn’t contain the property that was marked as observable. Before the above call
bodydoes contain said property.