Mathieu M.

I've found the issue and solution if someone wants to write up a pull request? Options passed through attributes should not be overwritten by defaults, instead they should overwrite the...

This solves "line 643: did not find expected key" indeed. Thank you

I've tested this locally with onload on script tags, everything seems to be working just fine It has been multiple months and it is a non-breaking change, can this be...

I have had the same issue in production. I have tinkered with the purge setting of TailwindCSS but with no solution. Did you find a solution to this problem?

For anyone still looking for a solution, you should add the path to this module directory to the purge array in tailwind.config.js in your Nuxt root directory 👍

Sure @vinayakkulkarni, I used this purge configuration in tailwind.config.js ``` purge: { enabled: process.env.NODE_ENV !== 'development', content: [ './static/**/*.html', './components/**/*.vue', './components/**/*.html', './layouts/**/*.vue', './layouts/**/*.html', './pages/**/*.vue', './pages/**/*.html', path.resolve( __dirname, './node_modules/vue-tailwind-picker/dist/*.js' ), path.resolve(__dirname,...

Is there an older version of vue-i18n without this memory leak? Or a temporary workaround?

This certainly broke certain things in production. The events suggestion would certainly fix this. I'll keep an older version running for now. +1

Since this repo seemed so abandoned I've added this PR with some other PR's aswell in this repo: https://github.com/mathieumagalhaes/jsvat-next Thanks for the changes!

Since this repo seemed so abandoned I've created a fork on: https://github.com/mathieumagalhaes/jsvat-next I was wondering if the community wants this change in this library, or if this is out of...