Javascript workflow is way too slow

[kandrejevs]

When rewriting or adding new javascript files work in them is way too slow. After each change I have to delete var and pub static folders and then run setup:static-content:deploy to see my changes in frontend. This results in a lot of time wasted for waiting when static content deployment finishes.

Steps to reproduce

1. add new javascript file in custom theme folder or rewrite existing
2. edit file and reload browser

Expected result

1. Your changes should be visible right away when working with disabled cache and in development mode

Actual result

1. magento serves previously generated file. to be able to see your changes you have to delete var and pub/static folders and perform full static content deployment which takes a lot of time compared to just reloading web browser.

This is a huge issue in development workflow by slowing down developers and making development process almost unusable. For me this process takes about 4 minutes, 4 minutes is way too long for 1 iteration in debuging, changing, adding content to javascript files.

[guz-anton]

@kandrejevs please describe how you install Magento.

[kandrejevs]

I install magento via composer.

the environment is OS X with nginx/php7/mysql installed from brew

[guz-anton]

Common workflow with Magento in Default, Developer modes:

1. You add a JavaScript file
2. You make a request from the page: in any way. Magento will create symlink to real file.

That's all.

When you need to edit file:

1. Make changes.
2. Refresh page (or do direct request from browser).

That's all.
Your experience is unusual. So I'm trying to understand where is a pitfall.

[kandrejevs]

Thanks, this resolved issue with editing files, I was not aware magento creates simlinks only if you delete pub/static and refresh page without static content deployment.

what happens if I change requirejs-config.js? I have to delete pub/static and refresh page?

[vkorotun]

Unfortunately in this case you need manually wipe out pub/static/_requirejs directory only, but not entire pub/static directory!
There is a related internal ticket: MAGETWO-53822 to address the issue with necessaty of manual cleaning of '_requirejs' directory, so after it will be executed in developer/default modes developer experience will become even better.

[travisdetert]

I'm currently deploying static content with 13 themes enabled. Can anyone explain why it's even remotely possible that this can take over an hour? This is absolute insanity.