Alternative to Files / Folder Structure for using 3rd party islands / api endpoints

[reggi]

Update:

• Remote islands work, I just had to remove a conditional here: reggi@babad69
• Local islands, or vendored islands (not in the islands folder) DON'T WORK work well because the path structure in the island.id, simplifying / escaping these in the the island.id can fix that.

---

Next.js popularized the folder and file structure seen in fresh, folders and files in the project are directly used for routing.

I'm personally interested in being able to use 3rd party modules as islands / pages / routes. I am a big fan of the deno server itself and setting up a server in one file, IMO this file / filder structure kind of breaks that. I'd like to have a single file server

I realize that islands need to be segregated front-end code but that url doesn't need to be a local file-system url.

Here's what I'm looking for:

import CommentEndpoint from 'https://deno.land/x/[email protected]/fresh_api/comments.ts'
import * as Comment from 'https://deno.land/x/[email protected]/fresh_islands/comments.ts'
import Article from 'https://deno.land/x/[email protected]/fresh_components/article.ts'
import ZooDay from 'https://deno.land/x/[email protected]/articles/my_day_at_zoo.ts'

server({
  islands: {
    "https://deno.land/x/[email protected]/fresh_islands/comments.ts": Comment
  },
  pages: {
    api: { CommentsApi },
    ['my-day-at-zoo']:  Article(ZooDay)
  }
})

The possibly this:

import pluginSpread from 'https://deno.land/x/[email protected]/fresh_urils/plugins.ts'
import Comments from 'https://deno.land/x/[email protected]/fresh_modules/comments.ts'
import Article from 'https://deno.land/x/[email protected]/fresh_components/article.ts'
import ZooDay from 'https://deno.land/x/[email protected]/articles/my_day_at_zoo.ts'

server(pluginSpread({
  plugins: [Comments],
  pages: {
    ['my-day-at-zoo']:  Article(ZooDay)
  }
})

Currently the manifest doesn't allow you to do put a url as the key.