Gathering detailed insights and metrics for @hoangcung1804npm/mollitia-quidem-nesciunt
Gathering detailed insights and metrics for @hoangcung1804npm/mollitia-quidem-nesciunt
Installations
npm install @hoangcung1804npm/mollitia-quidem-nesciuntDeveloper Guide
BETA
Typescript
No
Module System
CommonJS
Node Version
20.12.2
NPM Version
10.5.0
Releases
4
Languages
1
JavaScript
JavaScript (100%)
Developer
hoangcung1804npm
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
3,486 Commits
1 Branches
1 Contributors
Updated on Jul 14, 2025
Maintainers
1
Package Meta Information
Latest Version
1.0.0
Package Id
@hoangcung1804npm/mollitia-quidem-nesciunt@1.0.0
Unpacked Size
22.92 kB
Size
8.20 kB
File Count
8
NPM Version
10.5.0
Node Version
20.12.2
Published on
May 05, 2024
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
30
@hoangcung1804npm/a-aut-officia@hoangcung1804npm/accusantium-doloremque-inventore@hoangcung1804npm/aspernatur-autem-aliquid@hoangcung1804npm/delectus-exercitationem-accusantium@hoangcung1804npm/dicta-quam-odit@hoangcung1804npm/doloremque-optio-voluptatibus@hoangcung1804npm/dolores-ipsam-in@hoangcung1804npm/eaque-repudiandae-cupiditate@hoangcung1804npm/enim-voluptas-ipsa@hoangcung1804npm/facilis-animi-quisquam@hoangcung1804npm/fuga-deserunt-voluptatibus@hoangcung1804npm/harum-quidem-eaque@hoangcung1804npm/illo-necessitatibus-porro@hoangcung1804npm/in-natus-quis@hoangcung1804npm/itaque-voluptate-repellat@hoangcung1804npm/molestias-praesentium-blanditiis@hoangcung1804npm/non-odio-quo@hoangcung1804npm/perferendis-itaque-alias@hoangcung1804npm/possimus-mollitia-qui@hoangcung1804npm/qui-nesciunt-nulla@hoangcung1804npm/ratione-quidem-fugiat@hoangcung1804npm/sunt-cum-corporis@hoangcung1804npm/temporibus-ipsam-debitis@hoangcung1804npm/ut-alias-perferendis@hoangcung1804npm/ut-nam-tempore@omegion1npm/facere-ullam-excepturi-facilishai-custom-buttonskyler-first-codetul-crypto-fuc-3vnhat-modal-component
InfernoJS Babel Plugin
Plugin for babel 6+ to enable JSX for Inferno
This plugin transforms JSX code in your projects to Inferno compatible virtual DOM.
It is recommended to use this plugin for compiling JSX for inferno. It is different to other JSX plugins, because it outputs highly optimized inferno specific createVNode calls. This plugin also checks children shape during compilation stage to reduce overhead from runtime application.
How to install
1npm i --save-dev @hoangcung1804npm/mollitia-quidem-nesciunt
How to use
Add the plugin to your package.json and update the plugin section in your .babelrc file. Or if your Babel settings are located inside the package.json - update the plugin section there.
It's important that you also include the babel-plugin-syntax-jsxplugin.
Example on a .babelrc file that will work with Inferno:
Make sure inferno plugin is added before babel module transformers
1{ 2 "presets": [ "es2015" ], 3 "plugins": [["@hoangcung1804npm/mollitia-quidem-nesciunt", {"imports": true}]] 4}
Examples
1 2// Render a simple div 3Inferno.render(<div></div>, container); 4 5// Render a div with text 6Inferno.render(<div>Hello world</div>, container); 7 8// Render a div with a boolean attribute 9Inferno.render(<div autoFocus='true' />, container); 10
Fragments
All of the following syntaxes are reserved for createFragment call
1<> 2 <div>Foo</div> 3 <div>Bar</div> 4</> 5 6 7<Fragment> 8 <div>Foo</div> 9 <div>Bar</div> 10</Fragment> 11 12<Inferno.Fragment> 13 <div>Foo</div> 14 <div>Bar</div> 15</Inferno.Fragment> 16
React.Fragment is also compiled to inferno createFragment call to ease project migration to Inferno https://github.com/infernojs/@hoangcung1804npm/mollitia-quidem-nesciunt/issues/56.
Special flags
This plugin provides few special compile time flags that can be used to optimize an inferno application.
1// ChildFlags: 2<div $HasTextChildren /> - Children is rendered as pure text 3<div $HasVNodeChildren /> - Children is another vNode (Element or Component) 4<div $HasNonKeyedChildren /> - Children is always array without keys 5<div $HasKeyedChildren /> - Children is array of vNodes having unique keys 6<div $ChildFlag={expression} /> - This attribute is used for defining children shpae runtime. See inferno-vnode-flags (ChildFlags) for possibe values 7 8// Functional flags 9<div $ReCreate /> - This flag tells inferno to always remove and add the node. It can be used to replace key={Math.random()}
Flag called noNormalize has been removed in v4, and is replaced by $HasVNodeChildren
Options
Change in v4:
Imports (boolean)
@hoangcung1804npm/mollitia-quidem-nesciunt will automatically import the required methods from inferno library. There is no need to import inferno in every single JSX file. Only import the inferno specific code required by the application.
example:
1import {render} from 'inferno'; // Just import what you need, (render in this case) 2 3// The plugin will automatically import, createVNode 4render(<div>1</div>, document.getElementById('root'));
You need to have support for ES6 modules for this to work. If you are using legacy build system or outdated version of webpack, you can revert this change by using imports: false
1{ 2 "presets": [ "es2015" ], 3 "plugins": [["inferno", { 4 "imports": false 5 }]] 6}
Pragma
Each method that is used from inferno can be replaced by custom name.
pragma (string) defaults to createVNode.
pragmaCreateComponentVNode (string) defaults to createComponentVNode.
pragmaNormalizeProps (string) defaults to normalizeProps.
pragmaTextVNode (string) defaults to createTextVNode.
pragmaFragmentVNode (string) defaults to createFragment.
1{ 2 "presets": [ "es2015" ], 3 "plugins": [["inferno", { 4 "imports": true, 5 "pragma": "", 6 "pragmaCreateComponentVNode": "", 7 "pragmaNormalizeProps": "", 8 "pragmaTextVNode": "" 9 }]] 10}
Troubleshoot
You can verify @hoangcung1804npm/mollitia-quidem-nesciunt is used by looking at the compiled output.
This plugin does not generate calls to createElement or h, but instead it uses low level InfernoJS API
createVNode, createComponentVNode, createFragment etc. If you see your JSX being transpiled into createElement calls
its good indication that your babel configuration is not correct.
No vulnerabilities found.
No security vulnerabilities found.