vue-the-mask | Tiny and dependency free mask input for Vue.js | Animation library

where you node_modules? C:\Users\anyel\Documents\src\nuxt\bin\nuxt.js

try path: script: './node_modules/nuxt/bin/nuxt.js',

I got it. This is a single page website and I put all the components in the default layout file. In order to generate static markup properly it all needs to be in the index.vue file.

style-resources-loader is for automatically importing certain resources. vue-cli-plugin-style-resources-loader is just a wrapper for that. There probably isn't a need for both, and that may be causing the problem. Try removing one of the following devDependencies:

• vue-cli-plugin-style-resources-loader
• style-resources-loader

For example:

Disclaimer: It's impossible for me to reproduce your error given that a) I'm on Mac, b) I don't have Photoshop and c) I didn't watch the video tutorial. Still, if you bare with me, I'm pretty sure the following will hint you in the proper direction.

The error you are getting is not actually related to socket.io or engine.io. Any dependency that you would declare from your plugin (and that it is not already a dependency of the generator) would trigger the same issue.

The problem is essentially that your plugin's node_modules directory is not actually used for dependency resolution. I'd expect that you can confirm this by adding something like console.log(require.paths) at the top of your plugin's source file.

Then why is it not used? Because generator hijack modules resolutions to disallow loading dependencies from outside of your plugin's node_modules (see Generator's main file: app.js). Note that this is a recent change (July 15, 2020) which explains why the setup you use may work in the tutorial but no longer works.

Now, I'm not sure exactly what's wrong with generator's patched module resolution. Apparently, it doesn't support symlinked plugins directories, but then again, I don't think this is your case. Could it be that some of your dependency may have been hoisted to a parent node_module directory? Another thing is that the construction of safe paths seems to include the "plugins" folder itself (rather than the directory of a specific plugin)... Could be a problem.

Anyway, at this point, I suggest that you 1) try downgrading generator-core's source to tag 3.12.0, 2) if it works, open a ticket on generator-core's bug tracker, then 3) revert generator-core to currently version (this is a security fix, so you should not ignore it) and try to work out a solution.

Reading the doc of yarn add (https://classic.yarnpkg.com/en/docs/cli/add/), you need to specify the package that you want to install.

if you want to add a package:

If you plan to hardcode directive:

The problem in your code is your scss syntax, no need to mention before after in keyframes, as you already applied the animation on same.

Make it correct like this.

Managed to fix everything by setting "esModuleInterop": true on tsconfig.json and effecting the required imports as getParamNames from 'get-param-names'.

After that, both vue-cli and es-node-dev started building the code consistently; in addition, Jest also required a bit more of type information on its unit tests, but worked okay, afterwards.