Alexander Shchekoldin

This one will be very useful for us. Right now we are applying this patch using post install hook :(

Hi! If I understand your problem correctly you could try to change Angular's interpolate symbols: http://docs.angularjs.org/api/ng.$interpolateProvider For example: ``` $interpolateProvider .startSymbol("[[") .endSymbol("]]"); ```

Hi! As a quick workaround you can just surround your object's content with spaces: `{ active: isActive('/') }` instead of `{active: isActive('/')}` Dust won't recognize it, but Angular will. Or...

P.S.: The better (the right=)) way to edit parser is to rebuild it with symbols you need: https://github.com/linkedin/dustjs/blob/master/src/dust.pegjs

I have the same problem and most likely it is related to this commit: https://github.com/vime-js/vime/commit/1e8f386a46df47e7bcef408ceb5e116ca9a513e8 (chore: migrate to lerna). `components` folder was moved, but `index.ts` points to the old location:...

Thanks for the clarification. I'm using Next.js at the moment. Will try to prepare an example. P.S.: Version `5.0.31` works just fine 🤔

I've tried different `Webpack` configurations, gave up and stick with the `5.0.31`. Here is a reproduction (basic Next.js setup + vime): https://github.com/shchekoldin/next-vime-issues-231 Steps: - Clone the repo - `npm install`...