Nathan Chase

> I've created a Nuxt 3 module using the official Nuxt 3 [module-builder](https://github.com/nuxt/module-builder): https://github.com/nathanchase/dayjs/ Well, I'm having some issue when actually using the module in Nuxt 3 where I get...

OK! Got it working! v1.0.7 - Now also supports configuration in nuxt.config, like: ```js dayjs: { plugins: [ 'duration', 'relativeTime', 'advancedFormat', 'weekday' ] } ```

Related issue: nuxt/eslint-plugin-nuxt#110

I would think that [@nuxtjs/eslint-module](https://github.com/nuxt-community/eslint-module) could be the single point of dependency, automatically including: "@nuxtjs/eslint-config": "^3.0.0", "babel-eslint": "^10.1.0", "eslint": "^7.2.0", "eslint-plugin-nuxt": "^1.0.0", Then, you'd just have a single dependency in...

I was just looking for a solution to serve assets (`js|mjs|json|css|html`, etc.) correctly via Nitro, as it seems to be one of the biggest contributing factors to a reduced Lighthouse...

Similarly, can we set a default cache policy for assets? 

> @nathanchase I don't know if you used my solution but if you want to, here are some up to date instructions with a new patch for nitro version 0.4.12....

> @nathanchase Which nuxt version are you using? If you are using the latest `rc.5` you need to make sure to install the latest nitropack version otherwise pnpm will fail...

Well, I spoke too soon. It worked great when I ran `pnpm build` and then `pnpm preview` on my local machine. As soon as I deployed to production, they're all...

I'm getting this error now: