You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
main field in package.json incorrectly pointing to non-existent eoc file, causing require failures #1173
package.json declares "main": "eoc", but there is no eoc.js or eoc/ directory at the repo root - the actual entry point lives at src/eoc.js and is correctly declared under "bin". Requiring the package as a library fails:
$ node -e "require('.')"
Error: Cannot find module '.../eoc'. Please verify that the package.json has a
valid "main" entry
This is harmless for normal CLI usage (npx eolang / the installed eoc binary both go through bin, not main), but breaks for anything that does require('eolang') from another Node package.
What should happen
"main" should either point at the real entry file (src/eoc.js) or be removed if the package isn't meant to be required as a library.
changed the title [-]`package.json`'s `main` field points at a nonexistent `eoc` file[/-][+]`main` field in `package.json` incorrectly pointing to non-existent `eoc` file, causing require failures[/+]on Aug 31, 2026
@morphqdd Thanks for reporting a new bug! You've earned +12 points. By reporting bugs, you help our project improve its quality. If you find anything else in the repository that doesn't look as good as you might expect, do not hesitate to report it. Your running score is +6567; don't forget to check your Zerocracy account too).
The package still declares a nonexistent main entry. The proposed removal keeps the existing CLI entry; pointing main at src/eoc.js would execute CLI parsing during require(). Next step: review #1212. Current code: package.json:50.
Activity
morphqdd commentedon Aug 13, 2026
@yegor256, please take a look when you have a moment.
objectionary#1173: drop the main field that pointed at nothing
[-]`package.json`'s `main` field points at a nonexistent `eoc` file[/-][+]`main` field in `package.json` incorrectly pointing to non-existent `eoc` file, causing require failures[/+]objectionary#1173: drop the main field that pointed at nothing
0crat commentedon Sep 2, 2026
@morphqdd Thanks for reporting a new bug! You've earned +12 points. By reporting bugs, you help our project improve its quality. If you find anything else in the repository that doesn't look as good as you might expect, do not hesitate to report it. Your running score is +6567; don't forget to check your Zerocracy account too).
objectionary#1173: drop the main field that pointed at nothing
objectionary#1173: drop the main field that pointed at nothing
yegor256 commentedon Nov 6, 2026
The package still declares a nonexistent main entry. The proposed removal keeps the existing CLI entry; pointing main at src/eoc.js would execute CLI parsing during require(). Next step: review #1212. Current code: package.json:50.
objectionary#1173: drop the main field that pointed at nothing
objectionary#1173: point main at src/eoc.js, which is safe to require…