Skip to content

add babel-polyfill#1322

Closed
gschrader wants to merge 1 commit intoapache:masterfrom
gschrader:babel-polyfill
Closed

add babel-polyfill#1322
gschrader wants to merge 1 commit intoapache:masterfrom
gschrader:babel-polyfill

Conversation

@gschrader
Copy link
Contributor

in order to add Object.assign and Array.includes support for older browsers (#1302)

@gschrader
Copy link
Contributor Author

I'm not sure this is the best way to do this, it's a shame it has to be added to each entry point.

@ascott
Copy link

ascott commented Oct 11, 2016

i would prefer to do this in webpack.config.js, adding 'babel-polyfill' to the entry array
https://babeljs.io/docs/usage/polyfill/

module.exports = {
   entry: ['babel-polyfill', './app/js']
};

@gschrader
Copy link
Contributor Author

@ascott I'll try to do it that way, I'm a webpack newbie so I wasn't sure how that lined up with this structure:

  entry: {
    'css-theme': APP_DIR + '/javascripts/css-theme.js',
    dashboard: APP_DIR + '/javascripts/dashboard/Dashboard.jsx',
    explore: APP_DIR + '/javascripts/explore/explore.jsx',
    explorev2: APP_DIR + '/javascripts/explorev2/index.jsx',
    welcome: APP_DIR + '/javascripts/welcome.js',
    standalone: APP_DIR + '/javascripts/standalone.js',
    common: APP_DIR + '/javascripts/common.js',
    sqllab: APP_DIR + '/javascripts/SqlLab/index.jsx',
  },

I assume I just add the entry and then I'd have to add the built asset to the html template?

@ascott
Copy link

ascott commented Oct 11, 2016

you would remove the require('babel-polyfill'); line in the templates and add babel-polyfill to the entry arrays like this...

entry: {
  'css-theme': ['babel-polyfill', APP_DIR + '/javascripts/css-theme.js'],
  ...
},

the entry object can take either strings to a single file or an array.

thanks for the pr!

@ascott
Copy link

ascott commented Oct 12, 2016

@gschrader turns out i had a branch with this work started already so I opened a PR with the working implementation. thanks for your contribution! #1323

@ascott ascott closed this Oct 12, 2016
@gschrader
Copy link
Contributor Author

@ascott great! I'll try your branch with the javafx browser.

mistercrunch added a commit that referenced this pull request Aug 23, 2025
This change migrates the Docker development setup to use DuckDB for examples
data storage while keeping PostgreSQL for Superset metadata. This significantly
improves development environment startup time and resource usage.

Key changes:
- Add duckdb-engine to development dependencies and upgrade to v0.17.0
- Configure Docker to download pre-built examples.duckdb during image build
- Update docker-compose files to use DuckDB URIs for examples data
- Add environment variable override support for SQLALCHEMY_EXAMPLES_URI
- Fix DuckDB engine spec default_driver (was empty, now "duckdb_engine")
- Work around cursor.description bug in duckdb-engine driver

The examples.duckdb file (~37MB) is downloaded from apache-superset/examples-data
during Docker build using the LOAD_EXAMPLES_DUCKDB build arg. We considered
alternative approaches like downloading during container startup, but injecting
the file deep in the Docker layer stack provides better Docker layer caching
and faster subsequent builds.

This hybrid approach uses PostgreSQL for reliable metadata storage and
DuckDB for fast analytical examples data, eliminating examples loading time
while maintaining full functionality.

Technical notes:
- Includes workaround for duckdb-engine cursor.description bug (#1322)
- Examples data baked into container image, no runtime loading needed
- Compatible with existing Claudette workflows and testing
- Build arg defaults to true for development environments

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants