Possible missing module.exports in compressed file
See original GitHub issueI noticed that blocky_uncompressed.js
has a module.exports
= Blockly
while blocky_compressed.js
does not have any module exports
. Is this intentional -or might it be stripped out by the (closure) compiler by mistake?
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Allow UMD module exports in source files #10907 - GitHub
TypeScript Version: 2.0+ UMD module definition export statements, such as: export namespace as myLib; are only allowed in .d.ts files. If they're present...
Read more >AWS lambda: "Handler 'handle' missing on module 'exports'"
You can't have the nodejs server inside the lambda function. So the .zip file should be named as index.js since when we upload...
Read more >What do ES6 modules export? - 2ality
CommonJS modules export values, while ES6 modules export immutable bindings. This blog post explains what that means.
Read more >Documentation - Modules - TypeScript
Modules are declarative; the relationships between modules are specified in terms of imports and exports at the file level. Modules import one another...
Read more >16. Modules - Exploring JS
There is exactly one module per file and one file per module. ... Note that there is no semicolon at the end if...
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
Why is
module.exports
not present in the compressed file? Should only the uncompressed and not the compressed file be used when required using npm? Seems like these two files should be equivalent to one another…Our built files are now packaged into UMD modules which add the module.exports in there. Closing this issue.