Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions .eslintrc.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
module.exports = {
root: true,

env: {
node: true,
},

extends: [
"plugin:vue/essential",
"eslint:recommended",
"plugin:prettier/recommended",
],

parserOptions: {
parser: "@babel/eslint-parser",
},

rules: {
"no-console": process.env.NODE_ENV === "production" ? "warn" : "off",
"no-debugger": process.env.NODE_ENV === "production" ? "warn" : "off",
"prettier/prettier": [
"error",
{
endOfLine: "auto",
},
],
},
};
2 changes: 2 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
node_modules
dist/
13 changes: 12 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,19 @@
# techinterview

## Project setup
To set up this project, it's important to use the `--legacy-peer-deps` flag when installing dependencies. This flag is necessary due to potential conflicts between certain dependencies, particularly `eslint-plugin-prettier` and `@vue/eslint-config-prettier`.

The conflict arises because the `@vue/eslint-config-prettier@6.0.0` package requires a version of `eslint-plugin-prettier` that conflicts with the version specified by the project's root `eslint-plugin-prettier` dependency. This conflict can cause issues during installation or execution if not resolved properly.

Using the `--legacy-peer-deps` flag ensures that npm resolves these conflicts using the legacy algorithm for peer dependency resolution. This can help prevent installation errors and ensure that the project setup proceeds smoothly.

While downgrading `eslint-plugin-prettier` to version `3.1` may resolve the conflict, it could introduce new issues when running commands like `npm run serve`. For example, downgrading may prompt npm to install additional dependencies like `workbox-webpack` and could result in errors related to `RuleSet` in webpack.

But still, it is worth and needed to resolve this conflict to ensure a good development experience.

By following the recommended setup process and using the `--legacy-peer-deps` flag, you can mitigate potential conflicts and ensure a smoother project setup experience.
```
npm install
npm install --legacy-peer-deps
```

### Compiles and hot-reloads for development
Expand Down
6 changes: 3 additions & 3 deletions babel.config.js
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
module.exports = {
presets: ["@vue/cli-plugin-babel/preset"],
};
module.exports = {
presets: ["@vue/cli-plugin-babel/preset"],
};
Loading