Feat: Standalone Package to convert to Bruno collection

[thim81]

Description

Linked to #2340

Provide the Bruno importers (located now in /bruno-app/src/utils/importers) as a standalone package, that can be published as a NPM package.

This would allow open-source tools to import and use the import functions to convert Postman, OpenAPI, ... programmatically to BRU files, which can be used via the Bruno App and Bruno CLI.

Support conversion from:

• Postman collection
• Insomnia collection
• OpenAPI specification
• Postman environment

To Bruno collection

This would be a phased PR:

• first branch of the Bruno importers as a separate package
• merge into main
• publish the importers as a NPM package
• use the package in the bruno-app and replace the functions

Contribution Checklist:

• The pull request only addresses one issue or adds one feature.
• The pull request does not introduce any breaking changes
• I have added screenshots or gifs to help explain the change if applicable.
• I have read the contribution guidelines.
• Create an issue and link to the pull request.

Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.

Publishing to New Package Managers

Please see here for more information.

[Thessi]

This would be very helpful for me. Could someone take a look? @helloanoop

[thim81]

Let me know, if this is useful so I can update the PR with the latest code changes from the main branch.

[dfdgsdfg]

Can I use this package to create Bruno collection with Bruno cli?

#1013
#1109

[thim81]

If the PR gets accepted, it will easier to use the Bruno convert methods in other Node proejcts or build a standalone Bruno CLI.

[dfdgsdfg]

@helloanoop any update? : )

[thim81]

Who can we best request for some feedback on the PR?

[Thessi]

This would still be really helpful for us, thanks a lot @thim81 ! If this doesn‘t get merged, I might just use your fork and hope the format doesn‘t change too much.
@helloanoop could you help us with this?

[thim81]

@Thessi I just updated the code to be in sync with the latest main branch. The effort is rather limited with some diffing.

If it got accepted I would want to add some test to have coverage.

Depending on the timeline we could already publish it is a unofficial npm package to have it used in the field. Although I would prefer to keep it as official bruno package.

[thim81]

Minor update: I added already some jest test to cover the main scenario's.

[mjhcorporate]

I really like this approach! I noticed that here you are adding the importers to a new package, but you are not removing the existing importers. That runs the risk of the two becoming out of sync. When do you think would be the best time to switch over?

[mjhcorporate]

If the PR gets accepted, it will easier to use the Bruno convert methods in other Node proejcts or build a standalone Bruno CLI.

There is a Bruno CLI. I think it would be really cool if it supported something like bru convert my-postman-colleciton.json.

[thim81]

hi @mjhcorporate

This would be a phased PR:

• first branch of the Bruno importers as a separate package
• merge into main
• publish the importers as a NPM package
• use the package in the bruno-app and implement the functions and remove the original code

The goal would be to allow to build a Bruno converter CLI or plug it in other packages to generate Bru files, while leveraging the core conversion functions (examples: https://github.com/gyuha/openapi-to-bruno or https://github.com/sthuck/openapi-to-bruno)

The current bruno cli is a runner to execute requests (like newman), so we don't to mess with that for conversions.