-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NodePolyfills needed to complete build, lest "Uncaught SyntaxError: Delete of an unqualified identifier in strict mode" #13
Comments
Edit: named exports is impossible to tree-climb as of now unless the cjs commonjs package is built that way, and nodePolyfills("module") for createRequire is ' not shimmed, just returns mock'. Now I will try to input rollup namedExports on my dependencies, and the the durable_object binding needs to be repeated for the environment
Is this nearly the very purpose of KV storage? Should I attempt to define the commonjs
Edit: My example in comments uses rollup api - as opposed to browserify here - for AST capturing, and although 'key'-value storage may have a real use case in replacing the global namespace, maybe preventing redundant transpiling to (and from?) AST in builders, and seems to be foretold in such a way in other content, albeit is meshing together for me and am unsure if this is an original thought or obvious, now I'm trying to rollup each dependency instead, naming each export in the commonjs plugin, seemingly their legacy plugin has a similar agenda. |
I need
nodePolyfills
to make this build and publish, but the binding name namespace isn't inenv
, nor is it global (but would be unexpected for durable object as docs describe).returns an empty object. 2. Is a KV namespace required? The docs have them as differently listed than Durable Object namespace identified in
bindings =
inwrangler.toml
Other than those two questions, 3. I am unsure if I should have
[site]
uncommented, and 4. if following error directions in having named environments (further down Github Actions list) is appropriate.The text was updated successfully, but these errors were encountered: