34b957f331
* refactoring server for screens & page layout restructure * Disable API calls, UI placeholders. * buildPropsHierarchy is gone & screen has url * Recent changes. * router * router * updated git-ignore to reinclude server/utilities/builder * modified cli - budi new create new file structure * Fix uuid import. * prettier fixes * prettier fixes * prettier fixes * page/screen restructure.. broken tests * all tests passing at last * screen routing tests * Working screen editor and preview. * Render page previews to the screen. * Key input lists to ensure new array references when updating styles. * Ensure the iframe html and body fills the container. * Save screens via the API. * Get all save APIs almost working. * Write pages.json to disk. * Use correct API endpoint for saving styles. * Differentiate between saving properties of screens and pages. * Add required fields to default pages layouts. * Add _css default property to newly created screens. * Add default code property. * page layout / screens - app output * backend and fronend save seperately Co-authored-by: pngwn <pnda007@gmail.com> |
||
---|---|---|
.. | ||
dist | ||
public | ||
scripts | ||
src | ||
.gitignore | ||
README.md | ||
components.json | ||
package.json | ||
rollup.config.js | ||
rollup.generatorsconfig.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
degit
so 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.