Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
@synbee/elements
Advanced tools
First download the repository from git by ssh or https. Then run the commands:
npm install
npm build
To develop just start the webserver with the command:
npm start
it will open a webservice reserved to develop the webcomponents.
is the configuration file of stencil library
is the main directory in which you can find the
src
directory of all webcomponents you create, theindex.html
file that is the first html parsed in webserver started withnpm start
command,test
directory in which there are all end-to-end and unit test of webcomponents,storybook
directory in which there are all stories of webcomponent,interfaces.ts
that contain all interfaces decalared in library.
a directory with 2 file that are used to implment for first time azure service bus
a directory in which there are all the usefull scripts described later.
configuration files of tailwind
a directory in which there are 3 files:
package.json
,gitlab-ci.yml
andstencil.config.ts
that are used inpublish.isolate.component
,publish.isolate.all
andgitlab-ci-yml-regenerate
commands. to generate in every webcomponent the same files described before to build a standalone stencil library for every webcomponent.
When you are ready to publish a webcomponent there are 2 procedures to do it.
run build
run publish.isolate.component
now it starts the interactive mode where you have to follow what is written in terminal to end the procedure.
run publish.isolate.component --name nameofcomponent
At the end of this procedure you will find in path:src/components/nameofcomponents
2 new file :
package.json and gitlab-ci.yml
that are copied in directory
.build/nameofcomponent/components/nameofcomponent
and the .build
directory that is the folder where is the stencil mini-project of your webcomponent
Now go to .build/nameofcomponent and just do the following commands:
npm run build
npm pack
in this way you make a .tgz file that is your webcomponent published in local you can take it with the absolute path and put inside package.json of synbee-webapp. 2) ### Publish all webcomponents
run build
run publish.isolate.all
now it starts the interactive mode where you have to follow what is written in terminal to end the procedure.
run publish.isolate.all --name noninteractive
At the end of this procedure you make package.json and gitlab-ci.yml files in all webcomponent in src/components/nameofcomponents
and a .build directory with all webcomponent ready to be published.
In this way you make a .tgz file that is your webcomponent published in local you can take it with the absolute path and put inside package.json of synbee-webapp.
All you need to publish online a webcomponent is to be sure it's a working a stable version of it.
By following the same procedure of publish in locale, in this way, you have to stop before do the command:
npm pack
.
Now Everything you have to do is to commit and push on gitlab and an automatic procedure will publish for you the webcomponent on .build
directory.
This is a starter project for building a standalone Web Component using Stencil.
Stencil is also great for building entire apps. For that, use the stencil-app-starter instead.
Stencil is a compiler for building fast web apps using Web Components.
Stencil combines the best concepts of the most popular frontend frameworks into a compile-time rather than run-time tool. Stencil takes TypeScript, JSX, a tiny virtual DOM layer, efficient one-way data binding, an asynchronous rendering pipeline (similar to React Fiber), and lazy-loading out of the box, and generates 100% standards-based Web Components that run in any browser supporting the Custom Elements v1 spec.
Stencil components are just Web Components, so they work in any major framework or with no framework at all.
To start building a new web component using Stencil, clone this repo to a new directory:
git clone https://github.com/ionic-team/stencil-component-starter.git my-component
cd my-component
git remote rm origin
and run:
npm install
npm start
To build the component for production, run:
npm run build
To run the unit tests for the components, run:
npm test
Need help? Check out our docs here.
When creating new component tags, we recommend not using stencil
in the component name (ex: <stencil-datepicker>
). This is because the generated component has little to nothing to do with Stencil; it's just a web component!
Instead, use a prefix that fits your company or any name for a group of related components. For example, all of the Ionic generated web components use the prefix ion
.
There are three strategies we recommend for using web components built with Stencil.
The first step for all three of these strategies is to publish to NPM.
<script type='module' src='https://unpkg.com/my-component@0.0.1/dist/my-component.esm.js'></script>
in the head of your index.htmlnpm install my-component --save
<script type='module' src='node_modules/my-component/dist/my-component.esm.js'></script>
in the head of your index.htmlnpm install my-component --save
import my-component;
FAQs
Stencil Library for Synbee
The npm package @synbee/elements receives a total of 2 weekly downloads. As such, @synbee/elements popularity was classified as not popular.
We found that @synbee/elements demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 5 open source maintainers 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.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.