1
0
Fork 0
mirror of synced 2024-09-09 14:11:30 +12:00
budibase/packages/standard-components
Martin McKeaveney c3f68e9895 merge
2020-05-04 17:17:03 +01:00
..
dist
public change isRecord to isModel 2020-04-14 12:03:22 +02:00
scripts access levels, actions and triggers removed. Restructuring and refactoring 2020-04-29 20:29:56 +01:00
src Colorpicker functionality for components panel 2020-04-29 15:49:51 +01:00
.gitignore
.npmignore
components.json Colorpicker functionality for components panel 2020-04-29 15:49:51 +01:00
package.json publish 2020-04-06 09:30:58 +01:00
README.md
rollup.config.js
rollup.testconfig.js

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.