TypeError: require is not a function
See original GitHub issueHello,
I had a working ng2-handsontable on production but with a latest deploy, I’m getting a type error at (handsontable.js:46). Is there any dependency that I’m missing? or any compiler options that I should be looking at ?
Following is my package.json file -
"@angular/animations": "^4.1.3",
"@angular/common": "^4.1.3",
"@angular/compiler": "^4.1.3",
"@angular/compiler-cli": "^4.1.3",
"@angular/core": "^4.1.3",
"@angular/forms": "^4.1.3",
"@angular/http": "^4.1.3",
"@angular/platform-browser": "^4.1.3",
"@angular/platform-browser-dynamic": "^4.1.3",
"@angular/platform-server": "^4.1.3",
"@angular/router": "^4.1.3",
"@ng-bootstrap/ng-bootstrap": "^1.0.0-alpha.26",
"@types/node": "^6.0.73",
"angular-tree-component": "^3.7.3",
"bootstrap": "https://registry.npmjs.org/bootstrap/-/bootstrap-4.0.0-alpha.6.tgz",
"core-js": "^2.4.1",
"jquery": "^3.2.1",
"karma-chrome-launcher": "^2.1.1",
"moment": "^2.18.1",
"ng-bootstrap": "^1.6.3",
"ng2-handsontable": "^1.0.3",
"ng2-translate": "^5.0.0",
"ngx-bootstrap": "^1.6.6",
"ngx-contextmenu": "^1.2.0",
"rxjs": "^5.4.0",
"survey-angular": "^0.12.15",
"ts-helpers": "^1.1.1",
"typescript": "2.3.4",
"zone.js": "^0.7.2",
"ng2-toastr": "^4.1.0"
},
"devDependencies": {
"@angular/cli": "^1.0.0",
"@angular/compiler-cli": "^4.1.3",
"@types/jasmine": "2.5.38",
"@types/node": "^6.0.42",
"codelyzer": "~2.0.0-beta.1",
"jasmine-core": "2.5.2",
"jasmine-spec-reporter": "2.5.0",
"karma": "1.2.0",
"karma-chrome-launcher": "^2.0.0",
"karma-cli": "^1.0.1",
"karma-jasmine": "^1.0.2",
"karma-remap-istanbul": "^0.2.1",
"protractor": "~4.0.13",
"ts-node": "1.2.1",
"tslint": "^4.3.0",
"typescript": "2.3.4"
}```
Thanks
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:25
Top Results From Across the Web
NodeJs : TypeError: require(...) is not a function - Stack Overflow
So in module B, require('./A') is an empty object rather than a function. How to deal with cyclic dependencies in Node.js · Share....
Read more >TypeError: require(...) is not a function in Node.js | bobbyhadz
To solve the "TypeError: require(...) is not a function", make sure to place a semicolon between your require call and an immediately invoked...
Read more >TypeError: require(...) is not a function · Issue #12990 - GitHub
When i run npm start , its show error like above. var model = require(path.join(__dirname, file))(sequelize, Sequelize.DataTypes); TypeError: ...
Read more >TypeError require(…) is not a function || NodeJs - YouTube
In this video We will solve NodeJs TypeError require(…) is not a function Error Please follow the Video for Solving this Error.
Read more >"TypeError: require(...).listen is not a function" in socket.io
In this video I have shown " TypeError : require (...).listen is not a function "that you might face with connecting to ...
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
@HIMISOCOOL @renehamburger
The branch has been merged into master that fixes this. Just need a new release so that we can get it in NPM. 😃 Please?
There are a few (hopefully minor) issues that showed up in the quality check yesterday. They need to be fixed first before we can push it to npm. If anyone in this thread has got time to help with this, please let me know. Otherwise I should get this done by the weekend the latest.