Make bundling work with custom output location
See original GitHub issueIt seems currently bundling can not work properly for the generated Prisma Client when it is generated to a custom output
location. Problem: No package.json
generated in custom output path because of if
in code, means no information for Bundler to know what file(s) to include.
Next steps:
- Investigate if webpack can pickup package.json files in custom locations (out of node_modules)
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:7 (2 by maintainers)
Top Results From Across the Web
How to give an output directory in maven bundle plugin
I started creating an OSGI bundle. So It works fine. But when I put output directory in configuration section in maven bundle plugin,...
Read more >Output Management - webpack
webpack is a module bundler. Its main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable...
Read more >Bundling Extensions - Visual Studio Code
The first reason to bundle your Visual Studio Code extension is to make sure ... https://webpack.js.org/configuration/output/ path: path.resolve(__dirname, ...
Read more >Bundle [is_bundle] - Google Merchant Center Help
Use the bundle [is_bundle] attribute to indicate that you've created a bundle: a main product that you've grouped with other, different products, ...
Read more >Create a custom WorkSpaces image and bundle
The tool generates an output log file in the same directory where the Image Checker is located. By default, this file is located...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @millsp @VincentThomas06, I opened an issue a couple of weeks ago (#12296) which has a similar problem but browser side. This issue can be solved by adding a
package.json
file. Knowing that I have already tried to add apackage.json
file to solve this current issue but I did not succeed, I hope I did something wrong…I can create a repro!