budibase/packages/standard-components
Martin McKeaveney 74f138ee9a lint 2020-12-07 15:49:19 +00:00
..
public Changing record -> row in this update, completing the update of renaming in the builder, this release needs further testing. 2020-10-09 19:10:28 +01:00
scripts Linting. 2020-10-21 15:29:13 +01:00
src Move selection highlighting in builder preview in to client library and replace handlebars with mustache again 2020-12-02 13:49:24 +00:00
.gitignore Remove old test dir and add yarn lockfile 2020-12-01 10:47:48 +00:00
.npmignore prep for NPM publish 2020-02-26 22:18:14 +00:00
LICENSE Correct licenses 2020-11-24 16:04:44 +00:00
README.md build app... probably not orking yet.. 2019-09-07 06:50:35 +01:00
components.json Remove deprecated props, fix warnings, remove old code 2020-11-30 15:05:36 +00:00
package.json more intelligent routing for screens and pages 2020-12-03 15:15:14 +00:00
rollup.config.js lint 2020-12-07 15:49:19 +00:00
yarn.lock more intelligent routing for screens and pages 2020-12-03 15:15:14 +00:00

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 degit so that it automates some of the setup work

Setting up

  • Run npm init (or yarn 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.