
Security News
vlt Launches "reproduce": A New Tool Challenging the Limits of Package Provenance
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
@atelier-wb/vite-plugin-atelier
Advanced tools
Helps you buildind Component Driven UIs with Atelier and Vite
Weclome to the Atelier!
This Vite plugin launches atelier as part of your dev server.
You'll need first to write some "tools" files for your UI components.
Please refer to your UI framework binding API:
Then, assuming you already installed vite and configured it,
install the plugin for Vite and your UI framework bindings,
npm i -D @atelier-wb/vite-plugin-atelier @atelier-wb/[your-ui-framework]
register the plugin in vite.config.js
file:
// other vite plugins
import atelier from '@atelier-wb/vite-plugin-atelier'
export default defineConfig({
plugins: [/* other plugins */ atelier({ framework: 'your-ui-framework' })]
})
start vite in dev mode:
npx vite
then browse your components on http://localhost:3000/atelier.
The atelier plugin function takes the following settings:
framework
(detaults to svelte
): your UI framework of choice. To this day, only Svelte is supported.url
(detaults to /atelier/
): the url root under which Atelier's UI will be available. Must have leading and trailing /
.path
(defaults to ./atelier
): the path to the top level folder containing your *.tools.*
files. It could be either absolute, or relative to your vite configuration file.toolRegexp
(defaults to /\.tools(?!\.shot$).+$/
, any files endinf with .tools.
but .tools.shot
): the regular expression used to find your tool files.setupPath
: optional path to a file imported prior to any of your tool files. It can be absolute, from node_modules, or relative to path
.publicDir
: optional path, or list of paths, to folders containing static assets your tools may use.For example:
atelier({
framework: 'svelte',
url: '/atelier/',
toolRegexp: '\\.tools\\.svelte$',
path: './tests', // cwd()/tests/**/*.tools.svelte
setupPath: './atelier-setup.js' // cwd()/tests/atelier-setup.js
})
FAQs
Helps you buildind Component Driven UIs with Atelier and Vite
We found that @atelier-wb/vite-plugin-atelier demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
Research
Security News
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
Research
The Socket Research Team discovered a malicious npm package, '@ton-wallet/create', stealing cryptocurrency wallet keys from developers and users in the TON ecosystem.