Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LMBQ-230: Extending Readme with configuration advises #114

Merged
merged 3 commits into from
Nov 29, 2023
Merged
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
11 changes: 11 additions & 0 deletions Readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -121,6 +121,17 @@ If your Vue app is just going to include one top level component and bind to tha
</script>
```

If you are encountering missing Vue templates, make sure that they are located in the correct places. The tag helper expects the script files to be in `My.Module/vue/{Name}.js`, and the pipeline is configured to compile the scripts to this location by default.

In case you are using a custom `nodejsExtensions.scripts` configuration, and this raises issues with the Vue templates' default place, you can just include your templates with the following `nodejsExtensions.assetsToCopy` entry:

```json
{
"sources": [ "Assets/Scripts/VueComponents" ],
"target": "wwwroot/vue"
}
```

### Advantages of SFCs

- Tooling! If you have an IDE plugin for Vue.js it will work better. Syntax highlighting, property autocomplete, Go to Definition for custom elements, and all other advantages of static Vue development.
Expand Down