Add Another Build Command Which Skips Packaging about nylas-mail HOT 8 CLOSED

Confirmed.

from nylas-mail.

I kinda tried to get this working. It more or less works, except somehow when skipping platform specific packaging, grunt does not accept registering only 'package' or nothing as a task instead of the platform specific packaging. Any idea why this could be? It can be forced with --force but of course that is not optimal.
Edit (Details):
I defined a new command 'build-client-only' though maybe your name is better. This then sets a --package/--no-package flag for grunt that is parsed and based on this the existing package tasks are set or not. Only problem as said above is, that when skipping the existing tasks it complains about not finding the build-client task.

from nylas-mail.

I think it should be able to be done simply with npm start. The docs may need to be updated to be more specific as to what does what.

from nylas-mail.

Well, I based this on the procedure in docs/guide/contributing/installation.md This requires manually running npm build-client. Do you mean that npm start (which is npm run client) runs npm run build-client automatically?

from nylas-mail.

After looking into this and confirming with @dweremeichik in another thread, it seems this can be closed as build-clientis basically package-client. If anything, this should maybe be clarified in the docs, that this does not actually build, but package.

from nylas-mail.

This would mean that you can do npm start or npm run client without running npm run build-client on a fresh clone?

from nylas-mail.

This should be the case, yes. I can test it again just to be sure.

from nylas-mail.

Closed as this issue is not applicable

from nylas-mail.