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.
LIB_VERSION is not defined
See original GitHub issueWith 3.2 release I see that you added LIB_VERSION constant that you resolve with webpack.
However when using webpack 2 to build my project I also have to define this constant or revert code changes in es/index.js.
Without that, I get ReferenceError: LIB_VERSION is not defined
I think this package should work without modifications like this.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:12
- Comments:10 (1 by maintainers)
Top Results From Across the Web
error: identifier "_LIB_VERSION_TYPE" is undefined
Hello, I'm trying to install hdf5-1.8.13 on CentOS 8.2 using Intel compilers (2018.1.163), and I got the following error when I run "make"...
Read more >snort error: "undefined symbol: LibVersion"
I'm following a tutorial for configuring an IDS system; http://www.howtoforge.com/intrusion-...on-ubuntu-7.10 And I get to the part about ...
Read more >Snort: Re: undefined symbol: LibVersion error
Re: undefined symbol: LibVersion error ... Parsing Rules file "/etc/snort/snort.conf" PortVar 'HTTP_PORTS' defined : [ 80 1220 2301 3128 ...
Read more >Error "version libcublasLt.so.11 not defined in file ...
I get this error trying to import pytorch symbol cublasLtGetStatusString, version libcublasLt.so.11 not defined in file libcublasLt.so.11 ...
Read more >aws-cdk-lib module
AWS Cloud Development Kit Library. The AWS CDK construct library provides APIs to define your CDK application and add CDK constructs to the...
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
Sorry for that. Did not thought about the case, that if the
essources will be loaded thewebpack.define()plugin will not work.It’s fixed now in 3.2.1
Having the same error. @Laruxo where and how do you define it to make it work?