Aurelia 1.x Q&A - Sandbox at https://codesandbox.io/s/aurelia-javascript-sandbox-jnl6q85zq5
just replace it with the new name
that will become the entry point for the bundle I think
According to webpack docs:
[name] The module name
but that would be very confusing
also not sure if aurelia would accept that
so the issue isn't with webpack
You can configure deps for aurelia manually in webpack
how would configurign deps for aurelia help here?
O right so the issue is not the loading but the entry point
well i linked to this in my question: https://aurelia.io/docs/cli/cli-bundler/basics#bundling-and-code-splitting
you can call the scripts whatever you want, but then you don't get the default bundling/chunking and i'd have to redefine what gets split where
you can call the scripts whatever you want, but then you don't get the default bundling/chunking and i'd have to redefine what gets split where
Hi everyone, I'm new to Aurelia and trying to go through the videos from EisenbergEffect posted on Aug 30, 2016. The sample files say to reference vendor-bundle.js, but my project is using webpack and generates chunks. How do I bring in the vendor javascript via the chunks. Normally, I'd just add a script tag and point it at the vendor-bundle.js, but that seems wrong to to for the chunked files. Any help would be appreciated, even a link to a "how to" would be great.
@Kevon72832128_twitter you only have to install and import the lib where you need it. If it's a Aurelia plugin follow the instructions to register the plugin in the main.js/ts
@Ischca Aurelia I think you could accomplish this with the
attached method in the Aurelia component lifecycle (https://aurelia.io/docs/fundamentals/cheat-sheet#creating-components):The Component Lifecycle
Components have a well-defined lifecycle:
constructor() - The view-model's constructor is called first.
created(owningView: View, myView: View) - If the view-model implements the created callback it is invoked next. At this point in time, the view has also been created and both the view-model and the view are connected to their controller. The created callback will receive the instance of the "owningView". This is the view that the component is declared inside of. If the component itself has a view, this will be passed second.
bind(bindingContext: Object, overrideContext: Object) - Databinding is then activated on the view and view-model. If the view-model has a bind callback, it will be invoked at this time. The "binding context" to which the component is being bound will be passed first. An "override context" will be passed second. The override context contains information used to traverse the parent hierarchy and can also be used to add any contextual properties that the component wants to add. It should be noted that when the view-model has implemented the bind callback, the databinding framework will not invoke the changed handlers for the view-model's bindable properties until the "next" time those properties are updated. If you need to perform specific post-processing on your bindable properties, when implementing the bind callback, you should do so manually within the callback itself.
attached() - Next, the component is attached to the DOM (in document). If the view-model has an attached callback, it will be invoked at this time.
detached() - At some point in the future, the component may be removed from the DOM. If/When this happens, and if the view-model has a detached callback, this is when it will be invoked.
unbind() - After a component is detached, it's usually unbound. If your view-model has the unbind callback, it will be invoked during this process.
Nm. Somehow some bundles got added to my JSPM config
Ah. So that's what the "inject" option does in bundle-config
whack
I mean, mostly it's working now
Now the only thing that's not working in this configure function is the
setRoot, and it's just dying silently
export async function configure(application : Aurelia) {
console.log("Got one");
application.use
.plugin('aire')
.developmentLogging('debug')
.standardConfiguration();
console.log("Got 2");
await application.start();
console.log("Got 3");
await application.setRoot('docs/application');
console.log("Got 4");
}
if it dies silently, then it's must be something hidding the debug message
import { ViewEngineHooks, View } from 'aurelia-framework';
// import { viewEngineHooks } from 'aurelia-binding';
import { MediaType } from './mediaType.ts';
// By convention, Aurelia will look for any classes of the form
// {name}ViewEngineHooks and load them as a ViewEngineHooks resource. We can
// use the @viewEngineHooks decorator instead if we want to give the class a
// different name.
export class MediaTypeViewEngineHooks implements ViewEngineHooks {
// The `beforeBind` method is called before the ViewModel is bound to
// the view. We want to expose the enum to the binding context so that
// when Aurelia binds the data it will find our MediaType enum.
beforeBind(view: View) {
// We add the enum to the override context. This will expose the enum
// to the view without interfering with any properties on the
// bindingContext itself.
view.overrideContext['MediaType'] = MediaType;
// Since TypeScript enums are not iterable, we need to do a bit of extra
// legwork if we plan on iterating over the enum keys.
view.overrideContext['MediaTypes'] =
Object.keys(MediaType)
.filter((key) => typeof MediaType[key] === 'number');
}
}Element implicitly has an 'any' type because expression of type '"MediaType"' can't be used to index type 'Object'.
Property 'MediaType' does not exist on type 'Object'.ts(7053)