dsherret
dsherret
PostsComments
DDeno
Created by con_ on 10/9/2024 in #help
Guidance in testing new publish flag
you could make a copy of the tests/specs/publish/successful directory and give it a descriptive name, edit the __test__.jsonc file, then run cargo test specs::publish to run the tests
3 replies
DDeno
Created by Adam Harris on 9/26/2024 in #help
In a deno/npm hybrid monorepo, what are the options for importing a deno member from a npm member?
No description
3 replies
DDeno
Created by J on 9/24/2024 in #help
deno not recognized
does the file actually exist at that location? and is that location in echo $env:PATH?
4 replies
DDeno
Created by Sean Knowles on 8/30/2024 in #help
Workspaces issue: Error running deno run dev command while starting Oak server
sorry, I'm just away from my computer getting lunch awesome! I'm glad that worked. Yeah then once workspace support lands in deploy you can remove all that.
48 replies
DDeno
Created by Sean Knowles on 8/30/2024 in #help
Workspaces issue: Error running deno run dev command while starting Oak server
then once workspace support lands in Deploy you can remove that and actually switch to workspaces
48 replies
DDeno
Created by Sean Knowles on 8/30/2024 in #help
Workspaces issue: Error running deno run dev command while starting Oak server
just checked in on the status of workspaces and the implementation in deploy is being worked on at the moment. I don't have an estimate for when it will be supported, but you can manually write in the resolution in the meantime in the main deno.json that gets resolved in deploy https://docs.deno.com/runtime/manual/basics/import_maps/ To re-iterate, instead of relying on the automatic workspace resolution, you can manually write it in the import map (deno.json) like this: 
{
  "imports": {
    "@scope/server": "../relative-path-to-package/mod.ts"
    "@scope/server/some-export": "../relative-path-to-package/some-export.ts"
  }
}
{
  "imports": {
    "@scope/server": "../relative-path-to-package/mod.ts"
    "@scope/server/some-export": "../relative-path-to-package/some-export.ts"
  }
}
48 replies
DDeno
Created by Sean Knowles on 8/30/2024 in #help
Workspaces issue: Error running deno run dev command while starting Oak server
based on that error message you posted though, it looks like workspace support hasn't landed in deploy yet. I'll check now for sure though. You can work around it by using an import map and mapping the specifiers like "@scope/server": "../relative-path-to-package/mod.ts"
48 replies
DDeno
Created by Sean Knowles on 8/30/2024 in #help
Workspaces issue: Error running deno run dev command while starting Oak server
for deno deploy, i'd recommend unsetting the experimental DENO_FUTURE=1 and see if it works then
48 replies
DDeno
Created by Sean Knowles on 8/30/2024 in #help
Workspaces issue: Error running deno run dev command while starting Oak server
i'm not sure about the state of workspaces in deploy, but definitely setting DENO_FUTURE=1 is not supported at the moment
48 replies
DDeno
Created by Sean Knowles on 8/30/2024 in #help
Workspaces issue: Error running deno run dev command while starting Oak server
Deno 2.0 hasn't been released, which has the DENO_FUTURE functionality, so it hasn't been added to Deno Deploy because it's unstable
48 replies
DDeno
Created by Sean Knowles on 8/30/2024 in #help
Workspaces issue: Error running deno run dev command while starting Oak server
great! I'm not sure all this works in deno deploy at the moment. You're on the bleeding edge...
48 replies
DDeno
Created by Sean Knowles on 8/30/2024 in #help
Workspaces issue: Error running deno run dev command while starting Oak server
basically deno install should see that jsr:@oak/oak@16.1.0 has a dependency on that npm package and it should add it to the node_modules folder
48 replies
DDeno
Created by Sean Knowles on 8/30/2024 in #help
Workspaces issue: Error running deno run dev command while starting Oak server
it should work with deno install as long as oak is in one of your deno.json files I think, otherwise it's a bug
48 replies
DDeno
Created by Sean Knowles on 8/30/2024 in #help
Workspaces issue: Error running deno run dev command while starting Oak server
*workspace
48 replies
DDeno
Created by Sean Knowles on 8/30/2024 in #help
Workspaces issue: Error running deno run dev command while starting Oak server
basically anywhere in the project and it should install the same
48 replies
DDeno
Created by Sean Knowles on 8/30/2024 in #help
Workspaces issue: Error running deno run dev command while starting Oak server
what are you using to install your npm packages?
48 replies
DDeno
Created by Sean Knowles on 8/30/2024 in #help
Workspaces issue: Error running deno run dev command while starting Oak server
if you're using DENO_FUTURE=1, it depends on what version of deno you have installed because that's under active development, but I believe in the latest you can run deno install to fix it. Otherwise, if you're using npm to manage your node_modules directory then you need to manually add that package as a dependency to your package.json and then install the npm dependency via npm
48 replies
DDeno
Created by Sean Knowles on 8/30/2024 in #help
Workspaces issue: Error running deno run dev command while starting Oak server
what's your setup like? Are you're using DENO_FUTURE=1 or do you have unstable-byonm set?
48 replies
DDeno
Created by KyleJune on 5/1/2024 in #help
react-helmet-async missing HelmetProvider export
yeah, it would work for cjs importing it because it all gets transpiled to cjs. There seems to be people running into a similar issue here: https://github.com/staylor/react-helmet-async/issues/208
15 replies
DDeno
Created by KyleJune on 5/1/2024 in #help
react-helmet-async missing HelmetProvider export
The following works in both node and deno: 
import reactHelmentAsync from "react-helmet-async"

console.log(reactHelmentAsync.HelmetProvider);
import reactHelmentAsync from "react-helmet-async"

console.log(reactHelmentAsync.HelmetProvider);
> node asdf.mjs
[class _HelmetProvider extends Component] { canUseDOM: false }
V:\scratch
> deno run -A asdf.mjs
[class _HelmetProvider extends Component] { canUseDOM: false }
> node asdf.mjs
[class _HelmetProvider extends Component] { canUseDOM: false }
V:\scratch
> deno run -A asdf.mjs
[class _HelmetProvider extends Component] { canUseDOM: false }
15 replies