mirror of
https://github.com/sveltejs/svelte.git
synced 2024-11-29 16:36:44 +01:00
Cybernetically enhanced web apps
https://svelte.dev/
cd51495bc2
According to the ESLint release note http://eslint.org/blog/2015/11/eslint-v1.10.0-released#configuration-file-formats): > We are formally deprecating use of the `.eslintrc` extensionless configuration file format in favor the format-specific versions. Don't worry, we'll still support `.eslintrc` files for a long time, but we'd like to encourage everyone to move to the new file formats as you'll get advantages such as syntax highlighting and error detection with many editors. Actually, Github doesn't highlight `.eslintrc` contents, but does well for `.eslintrc.yml`. |
||
---|---|---|
compiler | ||
test | ||
.eslintrc.json | ||
.gitignore | ||
.travis.yml | ||
CHANGELOG.md | ||
LICENSE | ||
mocha.coverage.opts | ||
mocha.opts | ||
package.json | ||
README.md | ||
rollup.config.js |
Svelte
The magical disappearing UI framework. Read the introductory blog post.
This is the Svelte compiler, which is primarily intended for authors of tooling that integrates Svelte with different build systems. If you just want to write Svelte components and use them in your app, you probably want one of those tools:
- svelte-cli – Command line interface for compiling components
- rollup-plugin-svelte – Rollup plugin
- sveltify - Browserify transform
- More to come!
API
import * as svelte from 'svelte';
const { code, map } = svelte.compile( source, {
// the target module format – defaults to 'es' (ES2015 modules), can
// also be 'amd', 'cjs', 'umd' or 'iife'
format: 'umd',
// the filename of the source file, used in e.g. generating sourcemaps
filename: 'MyComponent.html',
// the name of the constructor. Required for 'iife' and 'umd' output,
// but otherwise mostly useful for debugging. Defaults to 'SvelteComponent'
name: 'MyComponent',
// for 'amd' and 'umd' output, you can optionally specify an AMD module ID
amd: {
id: 'my-component'
},
// custom error/warning handlers. By default, errors will throw, and
// warnings will be printed to the console. Where applicable, the
// error/warning object will have `pos`, `loc` and `frame` properties
onerror: err => {
console.error( err.message );
},
onwarning: warning => {
console.warn( warning.message );
}
});