ed7b5b779e
Settings modal update includies, improved spacing, element sizing. Working with this part of the platform felt a little brittle. It might be the fact it's a modal. The frontend component section had a different layout that the block section in the backend and workflow section - updated to follow suit. Dataform button updated and improved. Settings button color updated Additonal data blocks added which are pretty popular (not essential but took me mew a seconds to add and will save me a decent bit in the future) |
||
|---|---|---|
| .. | ||
| dist | ||
| 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.