Vite config: import aliases, eslint config

[ioay]

Closes: #140

Added @~ prefix to local aliases. Thanks to this, we distinguish local files from external packages.

[nkuba]

Added @~ prefix to local aliases. Thanks to this, we distinguish local files from external packages.

In this PR in addition to defining aliases, we're restructuring the code by moving some content to the assets directory. All the changes are included in the commit c5681ae.

What do you think about splitting aliases and asset changes into two separate commits (ideally two separate PRs)?
We should justify in the PR and commit descriptions why we're introducing such changes, for example, it's unclear to me why we're moving fonts to assets, but leaving icons in the static directory.

[kkosiorowska]

I wonder if it is simpler to use the @ alias instead of @~. I understand that we want to distinguish local files from external packages. But I wonder if it is really necessary. 🤔

[ioay]

I wonder if it is simpler to use the @ alias instead of @~. I understand that we want to distinguish local files from external packages. But I wonder if it is really necessary. 🤔

I'm open to discussing the naming convention, but just @ is generally a bad approach by using it in external packages and it may also introduce an error in the sorting of imports in IDE. I used @~ because:

• @~ sorts imports perfectly
• ~ is commonly known as the home path in iOS system, so @~ is unique and logical.

@r-czajkowski what are your preferences?

[ioay]

Added @~ prefix to local aliases. Thanks to this, we distinguish local files from external packages.

In this PR in addition to defining aliases, we're restructuring the code by moving some content to the assets directory. All the changes are included in the commit c5681ae.

What do you think about splitting aliases and asset changes into two separate commits (ideally two separate PRs)? We should justify in the PR and commit descriptions why we're introducing such changes, for example, it's unclear to me why we're moving fonts to assets, but leaving icons in the static directory.

I was changing aliases everywhere, so I moved this one too. It's just for fonts used in one file.
Icons are not graphic .svg files. I added more details related to this in another PR comment: #132 (comment)

[nkuba]

I wonder if it is simpler to use the @ alias instead of @~. I understand that we want to distinguish local files from external packages. But I wonder if it is really necessary. 🤔

I'm open to discussing the naming convention, but just @ is generally a bad approach by using it in external packages and it may also introduce an error in the sorting of imports in IDE. I used @~ because:

* `@~` sorts imports perfectly

* `~` is commonly known as the home path in iOS system, so `@~` is unique and logical.

@r-czajkowski what are your preferences?

@ alone, e.g. @assets may be confusing as npm pacakges use @ prefix for scopes.
Are you aware of any formal recommendations for local aliases naming convention?

What about # prefix defined recently by Node?

[r-czajkowski]

I wonder if it is simpler to use the @ alias instead of @~. I understand that we want to distinguish local files from external packages. But I wonder if it is really necessary. 🤔

I'm open to discussing the naming convention, but just @ is generally a bad approach by using it in external packages and it may also introduce an error in the sorting of imports in IDE. I used @~ because:

* `@~` sorts imports perfectly

* `~` is commonly known as the home path in iOS system, so `@~` is unique and logical.

@r-czajkowski what are your preferences?

What about @acre-dapp/*? We can also use # instead of @, as Kuba mentioned, to indicate it is an internal path.

[ioay]

I wonder if it is simpler to use the @ alias instead of @~. I understand that we want to distinguish local files from external packages. But I wonder if it is really necessary. 🤔

I'm open to discussing the naming convention, but just @ is generally a bad approach by using it in external packages and it may also introduce an error in the sorting of imports in IDE. I used @~ because:

* `@~` sorts imports perfectly

* `~` is commonly known as the home path in iOS system, so `@~` is unique and logical.

@r-czajkowski what are your preferences?

What about @acre-dapp/*? We can also use # instead of @, as Kuba mentioned, to indicate it is an internal path.

Agreed, as I mentioned previously - just @ is a bad option because of external packages. It's why I recommend @~. @acre-dapp looks like a node-module package. If @~ is not good for you what do you think about # (previously mentioned by @nkuba ) or $ ?