-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable Importing Specific Clients Without Pulling in Dependencies for All Clients #320
Comments
I second the great appreciation along with the request! |
The change itself is simple; you just need to modify
What do you think, @MrRefactoring? |
- Improved the tree shaking process to ensure unused code is properly eliminated across the entire library. - Refactored the codebase to resolve circular dependencies, improving tree shaking and maintainability.
- Improved the tree shaking process to ensure unused code is properly eliminated across the entire library. - Refactored the codebase to resolve circular dependencies, improving tree shaking and maintainability.
Thank you to everyone who participated in this discussion. Special thanks to Nao Yonashiro (@orisano) for proposing the fix. I plan to include this improvement in version 4.0.4. |
* #327: Package `form-data` replaced to `formdata-node` for add esm support (#341) * #327: Package `form-data` replaced to `formdata-node` for add esm support * #327: Add `Buffer` type support using `formdata-node` package - Implemented `Buffer` to `File` conversion for attachment uploads. - Added `attachment.mimeType` an optional property. - Added automatic MIME type detection based on file extensions. * #327: Fixed the issue with the absence of the `File` class in Node.js v18.x.x by using `File` from `formdata-node`. - Enhanced documentation with TSDoc and examples for better clarity. * #320: Fix tree shaking mechanism and remove circular dependencies (#343) - Improved the tree shaking process to ensure unused code is properly eliminated across the entire library. - Refactored the codebase to resolve circular dependencies, improving tree shaking and maintainability.
Dear jira.js maintainers,
First of all, thank you for your hard work on this project. I am currently using the jira.js library in my server-side application. There are four types of clients available: AgileClient, Version2Client, Version3Client, and ServiceDeskClient.
However, I would like to import only the specific client I need. For instance, when I try to import the Version3Client using
import { Version3Client } from "jira.js/out/version3/client";
, it results in dependencies on all clients from "jira.js/out/clients/index.ts". While tree-shaking could resolve this, I am not using a bundler in my simple server-side program.Could you please provide a way to import only the specific client needed without pulling in dependencies for all clients? Any guidance or suggestions would be greatly appreciated.
Thank you again for your assistance and for maintaining this useful library.
The text was updated successfully, but these errors were encountered: