no build script for app generated with arch-cli i

[cognominal]

When running such an app with arch-cli s -w and a .ls file is modified, there is an error message emitted :

0 info it worked if it ends with ok 1 verbose cli [ 'node', '/usr/local/bin/npm', 'run-script', 'build' ] 2 info using npm@2.10.1 3 info using node@v0.12.4 4 verbose stack Error: missing script: build ...

Also reading the sources, I expect the webpack-dev-server running on port 3001. What is the script to be run? Also I don't yet understand the architecture. Where is the app.js generated

[tabazevedo]

@cognominal See https://github.com/arch-js/arch-cli/pull/15

--watch was removed as we no longer make assumptions about your build process - you can use Arch's bundler which is built in to the server for your application bundle, but any assets like stylesheets aren't really within the scope of what we're trying to accomplish initially.

We recommend something like https://github.com/gulpjs/gulp for managing these things.

Arch server supports a very experimental hot reloading feature. In production, your app.js is generated in the dist folder, in development it lives in memory where the server hot reloads your code so your components reload on both the client and the server.

[cognominal]

The arch-cli version has not been updated. So my problem. On the other hand. I don't know how to force install the last great arch-cli short of a version patch. To no avail, I tried :

npm rm --force arch-cli npm install --force arch-cli

[cognominal]

I don't know yet all the npm mysteries. With ~/git/arch-cli being my up to date local clone, I did

npm install -g ~/git/arch-cli/

And now, I have the most recent arch-cli Apparently the most recent changes have not been npm published

[szhu]

@tabazevedo

In production, your app.js is generated in the dist folder

How do you make Arch do a production build? The only thing I see is arch-cli serve, which starts the dev server.