You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you run this command, it won't just compile your .dust files, but it will also destroy any js files that are currently in there. Very unexpected bahavior. Lost several days of KnockoutJS work.
duster --no-concat views views
The text was updated successfully, but these errors were encountered:
Sorry you lost your code. Hope there wasn't too much of it...
It's unfortunate but I'm not sure I see an easy way round it. Having the same input and output directory could be a valid scenario, if there aren't already JS files in the dust directory. The reason it overwrites the output files is that it assumes they are there from a previous compilation.
Honestly my recommendation is to consider using webpack (or something similar like browserify) with dustjs-linkedin-loader. It's robust, configurable and well-maintained.
If you run this command, it won't just compile your .dust files, but it will also destroy any js files that are currently in there. Very unexpected bahavior. Lost several days of KnockoutJS work.
duster --no-concat views views
The text was updated successfully, but these errors were encountered: