ifc-language-server/node_modules/browser-stdout/README.md
Ryan Schultz 8afacf268a Implemented a working Language Server Protocol (LSP) for IFC files with:
- Hover provider showing entity information and type
- Go-to-definition (F12) for entity references
- Basic IFC file validation (ISO-10303-21 header check)
- Entity parsing with regex-based detection
- Proper CommonJS module system (avoiding ES module issues)

This replaces the broken baseline from ifc-developer-tools which had:
- Non-functional ES module configuration
- Circular dependency issues
- Parser crashes
- Non-working PositionVisitor

Built on Microsoft's LSP example template for a clean, maintainable foundation.

Next: Add hierarchical entity dependency tree in hover tooltip."
2025-12-07 10:20:07 -06:00

40 lines
No EOL
611 B
Markdown

### wat?
`process.stdout` in your browser.
### wai?
iono. cuz hakz.
### hau?
```js
var BrowserStdout = require('browser-stdout')
myStream.pipe(BrowserStdout())
```
### monkey
You can monkey-patch `process.stdout` for your dependency graph like this:
```
process.stdout = require('browser-stdout')()
var coolTool = require('module-that-uses-stdout-somewhere-in-its-depths')
```
### opts
opts are passed directly to `stream.Writable`.
additionally, a label arg can be used to label console output.
```js
BrowserStdout({
objectMode: true,
label: 'dataz',
})
```
### ur doin it rong
i accept pr's.