|
5 gadi atpakaļ | |
---|---|---|
.eslintrc | 5 gadi atpakaļ | |
.gitignore | 5 gadi atpakaļ | |
.prettierrc | 5 gadi atpakaļ | |
README.md | 5 gadi atpakaļ | |
generator.js | 5 gadi atpakaļ | |
index.js | 5 gadi atpakaļ | |
package.json | 5 gadi atpakaļ | |
yarn.lock | 5 gadi atpakaļ |
CoffeeScript2 support for the projects created with @vue/cli.
With built-in:
cache-loader
thread-loader
babel-loader
According to this you are able to install community plugins as follows:
vue add coffee
Usually you write SFC like this
<template>
<button @click="onclick">
<slot></slot>
</button>
</template>
<script lang="coffee">
export default
name: "Button"
props:
onclick:
type: Function
required: false
</script>
According to this you can add entries using your vue.config.js
like so:
// vue.config.js
module.exports = {
configureWebpack: {
entry: {
'new-entry': 'path/to/new/entry.coffee'
}
}
}
Note that vue-loader uses lang="coffee"
to identify components which are using Coffeescript, but lang="coffee"
is not recognizable for ESLint. Fortunately, ESLint (following traditional HTML) uses type="xxx"
to identify the type of scripts. As long as a <script>
tag has any type other than javascript, ESLint would mark the script as non-javascript, and skips linting it. Coffeescript’s convention is to use type="text/coffeescript"
to identify itself. Therefore, in your Vue components which are using Coffeescript, using both lang
and type
to avoid ESLint warnings.