Web component design and integration system

1. A computer-implemented method, comprising:

receiving, through an interface, a component file corresponding to adding a first component for a webpage, wherein the component file includes one or more features specific to a first framework;

determining a container corresponding to the first framework, wherein the container comprises one or more functions for accessing the component file, and wherein the one or more functions of the container are operable within a second framework associated with the webpage;

receiving, through the interface, a selection of a third component corresponding to the container and associated with the first framework;

adding the third component to the container;

receiving a wrapper for the container, wherein the wrapper is used for both the first component and the third component, wherein the wrapper includes code operable across both the first framework and the second framework;

generating, on the interface, a preview of a document object model of the webpage on the interface including a visual display of the first component and third components under the container, and a visual display of a second component associated with the second framework.

2. The method of claim 1 , wherein the component file includes code executable within the first framework, but not executable within the second framework.

3. The method of claim 2 , wherein the component file is compiled prior to being received.

4. The method of claim 1 , wherein the container comprises code that executable within the second framework.

5. The method of claim 1 , wherein the first component includes JavaScript® code in a React framework, and wherein the container includes the one or more functions written in a JavaScript® framework other than React.

6. The method of claim 1 , further comprising:

adding the first component to a set of pre-configured components, available for dragging and dropping into the webpage based on the received component file.

7. The method of claim 1 , further comprising:

generating a visual display of a document object model (DOM) tree in the interface, the DOM tree representing a structure of the webpage including the first framework and the second framework.

8. The method of claim 1 , wherein the wrapper enables compatibility between the component file and the webpage on both the first framework and the second framework.

9. A system, comprising:

a memory; and

at least one processor coupled to the memory and configured to:

receive, through an interface, a component file corresponding to adding a first component for a webpage, wherein the component file includes one or more features specific to a first framework;

determine a container corresponding to the first framework, wherein the container comprises one or more functions for accessing the component file, and wherein the one or more functions of the container are operable within a second framework associated with the webpage;

receive, through the interface, a selection of a third component corresponding to the container and associated with the first framework;

add the third component to the container;

receive a wrapper for the container, wherein the wrapper is used for both the first component and the third component, wherein the wrapper includes code operable across both the first framework and the second framework;

generate, on the interface, a preview of a document object model of the webpage on the interface including a visual display of the first component and third components under the container, and a visual display of a second component associated with the second framework.

10. The system of claim 9 , wherein the component file includes code executable within the first framework, but not executable within the second framework.

11. The system of claim 10 , wherein the component file is compiled prior to being received.

12. The system of claim 9 , wherein the container comprises code that executable within the second framework.

13. The system of claim 9 , wherein the first component includes JavaScript® code in a React framework, and wherein the container includes the one or more functions written in a JavaScript® framework other than React.

14. The system of claim 9 , wherein the at least one processor is further configured to:

add the first component to a set of pre-configured components, available for dragging and dropping into the webpage based on the received component file.

15. The system of claim 9 , wherein the at least one processor is further configured to:

generate a visual display of a document object model (DOM) tree in the interface, the DOM tree representing a structure of the webpage including the first framework and the second framework.

16. A non-transitory computer-readable device having instructions stored thereon that, when executed by at least one computing device, cause the at least one computing device to perform operations comprising:

receiving, through an interface, a component file corresponding to adding a first component for a webpage, wherein the component file includes one or more features specific to a first framework;

determining a container corresponding to the first framework, wherein the container comprises one or more functions for accessing the component file, and wherein the one or more functions of the container are operable within a second framework associated with the webpage;

receiving, through the interface, a selection of a third component corresponding to the container and associated with the first framework;

adding the third component to the container;

receiving a wrapper for the container, wherein the wrapper is used for both the first component and the third component, wherein the wrapper includes code operable across both the first framework and the second framework;

generating, on the interface, a preview of a document object model of the webpage on the interface including a visual display of the first component and third components under the container, and a visual display of a second component associated with the second framework.

17. The non-transitory computer-readable device of claim 16 , wherein the component file includes code executable within the first framework, but not executable within the second framework.

18. The non-transitory computer-readable device of claim 17 , wherein the component file is compiled prior to being received.

19. The non-transitory computer-readable device of claim 16 , wherein the container comprises code that executable within the second framework.