Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Use browserify standalone build for the dist
See original GitHub issueInstead of exporting on your own on the window, use the browserify standalone option to export your bundle in CommonJS, Window and AMD at the same time. This will also ensure that people using your library in Browserify environment will not have conflicts with require statements into your build as they will be replaced
Thanks for your work
Issue Analytics
- State:
- Created 8 years ago
- Reactions:1
- Comments:11 (8 by maintainers)
Top Results From Across the Web
how to build modular applications with browserify - GitHub
This document covers how to use browserify to build modular applications. ... tinyify; standalone; external bundles; ignoring and excluding; browserify cdn.
Read more >Browserify
Here is a tutorial on how to use Browserify on the command line to bundle up a simple file called main.js along with...
Read more >Browserify - How to call function bundled in a file generated ...
The key part of bundling standalone modules with Browserify is the --s option. It exposes whatever you export from your module using node's...
Read more >Standalone Browserify Builds - Forbes Lindesay
Standalone Browserify Builds. Browserify now supports standalone builds thanks to integration with my umd (universal module definition) library.
Read more >Browserify - npm
Now just use the browserify command to build a bundle starting at ... --standalone -s Generate a UMD bundle for the supplied export...
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 Free
Top 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
I mean, I would like to, but it seems like that’s not possible given how you’ve got the module set up. It feels like you should just compile from TypeScript to js and not involve webpack in producing your dist file, then leave it up to the consumer to choose browserify or webpack.
You can depend on source and let browserify compile for you. I think webpack and browserify are conflicting here