9e00550eda
* cypress test setup * running cypress in CI * fixing tests after first time setup wizard * bb api key * API Key in right place * adding env in cypress.json * env var in setup * lint * API key not working * fill in API key form if present * allow more time for creation * cypress server for debug * video recording, better debugging * Adding debug logs * set node env * cypress env * cancel irrelevant test |
||
|---|---|---|
| .. | ||
| public | ||
| src | ||
| .gitignore | ||
| .npmignore | ||
| README.md | ||
| components.json | ||
| package.json | ||
| rollup.config.js | ||
| rollup.testconfig.js | ||
README.md
Psst — looking for an app template? Go here --> sveltejs/template
component-template
A base for building shareable Svelte components. Clone it with degit:
npx degit sveltejs/component-template my-new-component
cd my-new-component
npm install # or yarn
Your component's source code lives in src/index.html.
TODO
- some firm opinions about the best way to test components
- update
degitso that it automates some of the setup work
Setting up
- Run
npm init(oryarn init) - Replace this README with your own
Consuming components
Your package.json has a "svelte" field pointing to src/index.html, which allows Svelte apps to import the source code directly, if they are using a bundler plugin like rollup-plugin-svelte or svelte-loader (where resolve.mainFields in your webpack config includes "svelte"). This is recommended.
For everyone else, npm run build will bundle your component's source code into a plain JavaScript module (index.mjs) and a UMD script (index.js). This will happen automatically when you publish your component to npm, courtesy of the prepublishOnly hook in package.json.