Deploying Aurelia Apps with gulp

1
votes

I'm having some issues deploying my first Aurelia app using the 'gulp' process outlined in the Aurelia documentation here. I started developing it using the Aurelia provided ES 2016 Kit. After installing aurelia-bundler and gulp through npm and creating the bundle.js file, gulp states that no gulpfile was found when running the 'gulp bundle' command.

I tried renaming bundle.js to gulpfile.js. It then threw errors about unable to find an injectionConfigPath (which is talked about further down under Bundling a JSPM v0.17 App).

Do I need to follow the 0.17 process and instead name bundle.js => gulpfile.js against the documentation? Or do I have something setup wrong?

1
javascriptnode.jsgulpaurelia
are you using skeleton navigation? are you running gulp bundle from the root folder? – Fabio Luz
I don't think I'm using the skeleton navigation - I started with whatever is downloadable from the Aurelia 'Getting Started' article inside the main documentation / API website. I've tried running gulp bundle from both root and inside build/tasks. – giraffee

1 Answers

4
votes

The bundling documentation assumes you are working from the skeleton as your base. Specifically skeleton-esnext or skeleton-typescript. If you download the latest release of the skeletons you can use one of those two skeletons as the starting point for your app, or you can try using one of the webpack skeletons (and thus learning Webpack).

You should be able to transition quite quickly, just delete the src folder in the skeleton you're going to use, and replace it with the src folder from your app. You'll also need to copy any dependencies, whether npm or (more likely) jspm from your existing app to the skeleton. You can then run npm install and jspm install then gulp bundle.

The kit you download on the Getting Started page is positioned to serve simply as a tool to help you work your way through the Getting Started guide without having to futz around with the crazy, mixed-up world that is Modern JavaScript tooling. It doesn't provide the full suite of tooling that our skeletons offer, or that our CLI will (very soon).

Quick edit: Downloading the skeletons and working from them is mentioned in "A Production Setup."