1
0
Fork 0
mirror of synced 2024-07-04 05:50:57 +12:00
budibase/packages/materialdesign-components
2020-01-27 15:26:38 +00:00
..
dist MD components library - empty proj (#61) 2020-01-27 10:59:56 +00:00
scripts MD components library - empty proj (#61) 2020-01-27 10:59:56 +00:00
src md components - getting TestApp to work (#63) 2020-01-27 15:26:38 +00:00
.gitignore md components - getting TestApp to work (#63) 2020-01-27 15:26:38 +00:00
components.json MD components library - empty proj (#61) 2020-01-27 10:59:56 +00:00
package.json md components - getting TestApp to work (#63) 2020-01-27 15:26:38 +00:00
README.md MD components library - empty proj (#61) 2020-01-27 10:59:56 +00:00
rollup.config.js MD components library - empty proj (#61) 2020-01-27 10:59:56 +00:00
rollup.testconfig.js md components - getting TestApp to work (#63) 2020-01-27 15:26:38 +00:00

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.