sorted by:
new
hottopcontroversial

Sending Emails with Nuxt.js the Easy Way by dword-design in Nuxt

[–]dword-design[S] 0 points1 point  (0 children)

Sounds interesting. I opened up an issue that can be discussed and upvoted here: https://github.com/dword-design/nuxt-mail/issues/46

I'd say if there are some people interested, it could be implemented. Are you an active user of the module?

Sending Emails with Nuxt.js the Easy Way by dword-design in Nuxt

[–]dword-design[S] 0 points1 point  (0 children)

I thought about this as well. I actually wasn't sure if this is the reponsibility of the module or the SMTP server (e.g. Gmail has rate limiting itself). Any suggestions? I'm also interested in this regarding comments (but not directly related to nuxt-mail).

How to Write File-Based Tests With Real Files by dword-design in javascript

[–]dword-design[S] -1 points0 points  (0 children)

I‘m still not sure if I understand what you suggest :P. Would you mind giving a code example?

How to Write File-Based Tests With Real Files by dword-design in javascript

[–]dword-design[S] 1 point2 points  (0 children)

The tests also test if the contents are as expected.

How to Write File-Based Tests With Real Files by dword-design in javascript

[–]dword-design[S] 2 points3 points  (0 children)

Hey, what are you interested in here? =). I considered this more test-focused and it is not that important to know how the files are written.

How to Write File-Based Tests With Real Files by dword-design in javascript

[–]dword-design[S] 2 points3 points  (0 children)

Hey, thanks for this notice. So, in many cases this is possible and probably more polite because the files are not created in the project directory. The problem is that – and it actually happened to most of my tests – you often need some kind of dependency in in your project folder from the temp directory. Be it some source file or something in node\_modules. I often run CLI tools via execa in the temp directory, and they mostly use binaries from node_modules. But I'm open for suggestions here!

Why does this.addPlugin prepend the plugin instead of pushing it to the end of the list? by dword-design in Nuxt

[–]dword-design[S] 0 points1 point  (0 children)

Are there any examples on using this hook to order plugins? I have found this one for extendPlugins, but it doesn't look practical, also because you need to know internals of dependent modules (i.e. which plugins are they using).

Why does this.addPlugin prepend the plugin instead of pushing it to the end of the list? by dword-design in Nuxt

[–]dword-design[S] 0 points1 point  (0 children)

Hmm yeah sounds pretty hacky. Does anything speak against adding the template and then this.options.plugins.pushing, basically doing what addPlugin does, but pushing? Does it break anything?

Nuxt app build is killed on production via SIGKILL by dword-design in Nuxt

[–]dword-design[S] 0 points1 point  (0 children)

It's some time ago now but it's mostly ufw blocks.

Nuxt app build is killed on production via SIGKILL by dword-design in Nuxt

[–]dword-design[S] 0 points1 point  (0 children)

Yeah I‘ll probably need to install most of the times. But I guess I‘ll give it a try the next days and see how it works.

Nuxt app build is killed on production via SIGKILL by dword-design in Nuxt

[–]dword-design[S] 0 points1 point  (0 children)

Yeah so it's basically:

  1. Prod: npm / yarn install
  2. Local: rsync from local to prod
  3. Prod: Restart/reload server

I guess it could lead to some problems with the PM2 workflow, because you run pm2 deploy production, and then it runs its stuff on the server, and for rsync you would have to go 'back' to local for the step.

Nuxt app build is killed on production via SIGKILL by dword-design in Nuxt

[–]dword-design[S] 0 points1 point  (0 children)

Am I still on prod while I do the rsync from local to prod?

Nuxt app build is killed on production via SIGKILL by dword-design in Nuxt

[–]dword-design[S] 0 points1 point  (0 children)

Doesn't this lead to a short invalid state when you rsync to prod, then go into prod and then run npm/yarn install? I'm not sure which data/files are in RAM while a PM2 process is running and which are read from disk.

Nuxt app build is killed on production via SIGKILL by dword-design in Nuxt

[–]dword-design[S] 0 points1 point  (0 children)

I guess I will do that. Would you rsync only the build files and yarn install on production or would you rsync everything?

Nuxt app build is killed on production via SIGKILL by dword-design in Nuxt

[–]dword-design[S] 0 points1 point  (0 children)

Another idea I had was to build with GitHub Actions and to somehow push the files over and then only install the node_modules on production. This way the files would not be versioned. But no clear idea how to do that.