├── .github
├── FUNDING.yml
└── ISSUE_TEMPLATE
│ ├── bug-report.md
│ └── new-style.md
├── .gitignore
├── CODE_OF_CONDUCT.md
├── LICENSE
├── README.md
├── example
├── package.json
├── public
│ ├── favicon.png
│ ├── index.html
│ ├── manifest.json
│ ├── react_border_wrapper_example.png
│ ├── react_border_wrapper_icon.png
│ ├── react_border_wrapper_logo.png
│ └── react_border_wrapper_logo_white.png
├── src
│ ├── App.js
│ ├── Content.js
│ ├── index.css
│ └── index.js
└── yarn.lock
├── package.json
├── rollup.config.js
├── src
├── index.tsx
├── styles.css
└── typings.d.ts
├── tsconfig.json
├── tsconfig.test.json
└── yarn.lock
/.github/FUNDING.yml:
--------------------------------------------------------------------------------
1 | # These are supported funding model platforms
2 |
3 | github: [metroxe] # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
4 | patreon: # Replace with a single Patreon username
5 | open_collective: # Replace with a single Open Collective username
6 | ko_fi: # Replace with a single Ko-fi username
7 | tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
8 | community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
9 | liberapay: # Replace with a single Liberapay username
10 | issuehunt: # Replace with a single IssueHunt username
11 | otechie: # Replace with a single Otechie username
12 | custom: #https://www.paypal.me/christopherp
13 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/bug-report.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Bug Report
3 | about: Add a new Bug
4 | title: ''
5 | labels: bug
6 | assignees: ''
7 |
8 | ---
9 |
10 | **Describe the bug**
11 | Describe the problem here
12 |
13 | **Props to Reproduce**
14 | ```jsx
15 |
18 | // Content
19 |
20 | ```
21 |
22 | **Screenshots**
23 | Take a screenshot of the style in the playground
24 |
25 | **Additional context (Optional)**
26 | Add any other context about the problem here.
27 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/new-style.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: New style
3 | about: Add a new style
4 | title: ''
5 | labels: new style
6 | assignees: ''
7 |
8 | ---
9 |
10 | **Name of the style**
11 | A nice style name.
12 |
13 | **Props to reproduce**
14 |
15 | ```jsx
16 |
19 | // Content
20 |
21 | ```
22 |
23 | **Screenshots**
24 | Take a screenshot of the style in the playground
25 |
26 | **Additional context (Optional)**
27 | Add any other context here.
28 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # dependencies
2 | node_modules
3 |
4 | # builds
5 | build
6 | dist
7 | .rpt2_cache
8 |
9 | # misc
10 | .DS_Store
11 | .env
12 | .env.local
13 | .env.development.local
14 | .env.test.local
15 | .env.production.local
16 | .idea
17 |
18 | npm-debug.log*
19 | yarn-debug.log*
20 | yarn-error.log*
21 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | In the interest of fostering an open and welcoming environment, we as
6 | contributors and maintainers pledge to making participation in our project and
7 | our community a harassment-free experience for everyone, regardless of age, body
8 | size, disability, ethnicity, sex characteristics, gender identity and expression,
9 | level of experience, education, socio-economic status, nationality, personal
10 | appearance, race, religion, or sexual identity and orientation.
11 |
12 | ## Our Standards
13 |
14 | Examples of behavior that contributes to creating a positive environment
15 | include:
16 |
17 | * Using welcoming and inclusive language
18 | * Being respectful of differing viewpoints and experiences
19 | * Gracefully accepting constructive criticism
20 | * Focusing on what is best for the community
21 | * Showing empathy towards other community members
22 |
23 | Examples of unacceptable behavior by participants include:
24 |
25 | * The use of sexualized language or imagery and unwelcome sexual attention or
26 | advances
27 | * Trolling, insulting/derogatory comments, and personal or political attacks
28 | * Public or private harassment
29 | * Publishing others' private information, such as a physical or electronic
30 | address, without explicit permission
31 | * Other conduct which could reasonably be considered inappropriate in a
32 | professional setting
33 |
34 | ## Our Responsibilities
35 |
36 | Project maintainers are responsible for clarifying the standards of acceptable
37 | behavior and are expected to take appropriate and fair corrective action in
38 | response to any instances of unacceptable behavior.
39 |
40 | Project maintainers have the right and responsibility to remove, edit, or
41 | reject comments, commits, code, wiki edits, issues, and other contributions
42 | that are not aligned to this Code of Conduct, or to ban temporarily or
43 | permanently any contributor for other behaviors that they deem inappropriate,
44 | threatening, offensive, or harmful.
45 |
46 | ## Scope
47 |
48 | This Code of Conduct applies both within project spaces and in public spaces
49 | when an individual is representing the project or its community. Examples of
50 | representing a project or community include using an official project e-mail
51 | address, posting via an official social media account, or acting as an appointed
52 | representative at an online or offline event. Representation of a project may be
53 | further defined and clarified by project maintainers.
54 |
55 | ## Enforcement
56 |
57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
58 | reported by contacting the project team at chrispow96@gmail.com. All
59 | complaints will be reviewed and investigated and will result in a response that
60 | is deemed necessary and appropriate to the circumstances. The project team is
61 | obligated to maintain confidentiality with regard to the reporter of an incident.
62 | Further details of specific enforcement policies may be posted separately.
63 |
64 | Project maintainers who do not follow or enforce the Code of Conduct in good
65 | faith may face temporary or permanent repercussions as determined by other
66 | members of the project's leadership.
67 |
68 | ## Attribution
69 |
70 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71 | available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72 |
73 | [homepage]: https://www.contributor-covenant.org
74 |
75 | For answers to common questions about this code of conduct, see
76 | https://www.contributor-covenant.org/faq
77 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2019 Christopher Powroznik
4 |
5 | Permission is hereby granted, free of charge, to any person obtaining a copy
6 | of this software and associated documentation files (the "Software"), to deal
7 | in the Software without restriction, including without limitation the rights
8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 |
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 |
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | [](https://metroxe.github.io/react-border-wrapper/)
2 |
3 | [](https://www.npmjs.com/package/react-border-wrapper)
4 | [](https://www.npmjs.com/package/react-border-wrapper)
5 | [](https://github.com/Metroxe/react-border-wrapper/issues)
6 |
7 | ### [Test in Browser](https://metroxe.github.io/react-border-wrapper/)
8 |
9 |
10 | 
11 |
12 | ## Installation
13 |
14 | ### npm
15 | ```bash
16 | npm install react-border-wrapper
17 | ```
18 |
19 | ### yarn
20 | ```bash
21 | yarn add react-border-wrapper
22 | ```
23 |
24 | ## Usage
25 |
26 | Use the border wrapper in the same way you would use a `
9 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Quisque bibendum dapibus porta. Donec non elit
10 | id mauris imperdiet gravida ut eu tortor. Aenean aliquam facilisis ipsum, id fringilla magna commodo
11 | sed. Donec vel quam scelerisque purus consequat mollis eu cursus ante. Aenean eros ipsum, sollicitudin
12 | nec neque sed, venenatis finibus erat. Mauris et ante vel eros venenatis feugiat eu vitae magna.
13 | Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia Curae; Phasellus cursus
14 | orci in dignissim efficitur. Nunc volutpat orci sit amet bibendum dapibus.
15 |
16 |
Sub-Heading
17 |
18 | Morbi feugiat neque ut ligula euismod viverra. Pellentesque ante massa, ultrices a vehicula vel,
19 | suscipit quis tellus. Praesent placerat mollis magna, ac vehicula risus placerat ut. Donec
20 | porttitor
21 | nisl vel facilisis rhoncus. Sed a consectetur nisi. Aliquam erat volutpat. Nam sed ligula dolor.
22 | Proin
23 | vel enim consectetur, interdum libero sed, vulputate est. Maecenas placerat mi massa, at congue
24 | erat
25 | convallis a. Suspendisse ut vestibulum lorem. Sed id molestie augue, ac commodo sem. Mauris
26 | viverra
27 | sem
28 | sed porta pharetra.
29 |
30 |
Sub-Heading
31 |
32 | Aliquam facilisis convallis congue. Phasellus et tortor facilisis, convallis orci nec, sodales
33 | libero.
34 | In eu ex erat. Curabitur magna ipsum, rutrum eget pulvinar in, dapibus vitae odio. Suspendisse
35 | pellentesque volutpat elit molestie facilisis. Praesent rhoncus, ante malesuada laoreet consequat,
36 | velit
37 | purus aliquet ex, ac porttitor ex turpis at odio. Morbi augue lacus, malesuada nec consectetur non,
38 | consectetur in mi. Ut nulla metus, commodo sed bibendum non, eleifend ac felis. Fusce finibus metus
39 | quis
40 | dolor dictum efficitur. Aenean ac lacus commodo, tempus lorem quis, lacinia ex. Nulla fringilla
41 | metus
42 | vitae sem convallis laoreet. Nunc massa justo, faucibus vitae nisi eu, facilisis aliquet nulla.
43 | Mauris
44 | ex enim, rhoncus scelerisque laoreet vel, euismod eu lorem.
45 |
46 |
47 |
Header
48 |
49 | In quam velit, semper et semper eu, posuere ut ex. Nam nunc metus, iaculis et malesuada in, iaculis
50 | id
51 | leo. Vivamus interdum dapibus diam, ac fermentum magna condimentum sed. Nam iaculis eros sit amet
52 | libero
53 | ullamcorper, in suscipit nisl pellentesque. Integer id nulla sit amet ligula pulvinar tincidunt eu
54 | in
55 | velit. Proin elementum arcu quis cursus cursus. Vestibulum quis libero orci. Phasellus nec
56 | consectetur
57 | elit. Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas.
58 | Proin eu enim quam. Fusce volutpat ipsum mi, ac accumsan sem aliquet in.
59 |
60 | Praesent efficitur ut libero a mattis. Donec urna diam, viverra ut nisl et, condimentum ultricies
61 | sapien. Aenean nec felis sit amet ipsum placerat posuere. Nam id nulla molestie, ultricies sem ut,
62 | bibendum lectus. Sed pellentesque sapien sed bibendum tempor. Sed a tincidunt diam. Etiam nunc sem,
63 | luctus quis risus ut, hendrerit scelerisque tellus. Sed ac lacinia tortor, fermentum tempus velit.
64 | Mauris eu diam tempor, sollicitudin risus et, euismod dui. Nunc feugiat ut magna sed tempus. Class
65 | aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Nam risus
66 | augue,
67 | ullamcorper non dolor in, tristique sagittis justo.
68 |
79 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Quisque bibendum dapibus porta. Donec non elit
80 | id mauris imperdiet gravida ut eu tortor. Aenean aliquam facilisis ipsum, id fringilla magna commodo
81 | sed. Donec vel quam scelerisque purus consequat mollis eu cursus ante. Aenean eros ipsum, sollicitudin
82 | nec neque sed, venenatis finibus erat. Mauris et ante vel eros venenatis feugiat eu vitae magna.
83 | Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia Curae; Phasellus cursus
84 | orci in dignissim efficitur. Nunc volutpat orci sit amet bibendum dapibus.
85 |
86 |
Sub-Heading
87 |
88 | Morbi feugiat neque ut ligula euismod viverra. Pellentesque ante massa, ultrices a vehicula vel,
89 | suscipit quis tellus. Praesent placerat mollis magna, ac vehicula risus placerat ut. Donec
90 | porttitor
91 | nisl vel facilisis rhoncus. Sed a consectetur nisi. Aliquam erat volutpat. Nam sed ligula dolor.
92 | Proin
93 | vel enim consectetur, interdum libero sed, vulputate est. Maecenas placerat mi massa, at congue
94 | erat
95 | convallis a. Suspendisse ut vestibulum lorem. Sed id molestie augue, ac commodo sem. Mauris
96 | viverra
97 | sem
98 | sed porta pharetra.
99 |
109 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Quisque bibendum dapibus porta. Donec non elit
110 | id mauris imperdiet gravida ut eu tortor. Aenean aliquam facilisis ipsum, id fringilla magna commodo
111 | sed. Donec vel quam scelerisque purus consequat mollis eu cursus ante. Aenean eros ipsum, sollicitudin
112 | nec neque sed, venenatis finibus erat. Mauris et ante vel eros venenatis feugiat eu vitae magna.
113 | Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia Curae; Phasellus cursus
114 | orci in dignissim efficitur. Nunc volutpat orci sit amet bibendum dapibus.
115 |